GNU bug report logs - #63655
29.0.91; Dialog box not displayed upon closing frame

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#63655: closed (29.0.91; Dialog box not displayed upon closing
 frame)
Date: Tue, 23 May 2023 14:49:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Tue, 23 May 2023 17:48:06 +0300
with message-id <83v8gjnly1.fsf <at> gnu.org>
and subject line Re: bug#63655: 29.0.91; Dialog box not displayed upon closing frame
has caused the debbugs.gnu.org bug report #63655,
regarding 29.0.91; Dialog box not displayed upon closing frame
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
63655: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=63655
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Po Lu <luangruo <at> yahoo.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 29.0.91; Dialog box not displayed upon closing frame
Date: Tue, 23 May 2023 13:12:38 +0800

Start Emacs, then set confirm-kill-emacs to t.
Close the last frame on the only terminal by clicking the close button
on the WM frame window.  Emacs will ask:

  Really exit Emacs? (y or n)

in the echo area, instead of displaying a popup dialog as in Emacs 28.
This makes it difficult to close Emacs using only the mouse.

[Message part 3 (message/rfc822, inline)]

From: Eli Zaretskii <eliz <at> gnu.org>
To: Po Lu <luangruo <at> yahoo.com>
Cc: 63655-done <at> debbugs.gnu.org
Subject: Re: bug#63655: 29.0.91; Dialog box not displayed upon closing frame
Date: Tue, 23 May 2023 17:48:06 +0300

> From: Po Lu <luangruo <at> yahoo.com>
> Cc: 63655 <at> debbugs.gnu.org
> Date: Tue, 23 May 2023 21:16:40 +0800
> 
> Yes, it does.  Thanks.

Thanks, installed on the release branch, after some cleanup and update
of the docs.

> BTW, could we please not change yes-or-no-p on the release branch?  It's
> not involved in y-or-n-p, and doing so makes me skittish for a reason
> you can surely understand.

I'm just being proactive -- the very next bug report we will get is
why yes-or-no-p behaves differently wrt use of dialog boxes.  Even in
the recipe you posted here, yes-or-no-p behaved differently.  It makes
no sense to me to have such subtle differences, especially when many
people replace one of these function by the other, and we even have a
user option nowadays to do that automatically.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.