all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 63655-done@debbugs.gnu.org
Subject: bug#63655: 29.0.91; Dialog box not displayed upon closing frame
Date: Wed, 24 May 2023 08:18:31 +0800	[thread overview]
Message-ID: <87ttw2vay0.fsf@yahoo.com> (raw)
In-Reply-To: <83v8gjnly1.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 23 May 2023 17:48:06 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> 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.

I think we really ought to wait until a complaint to make this change on
emacs-29.  I'm fine with doing it on master.

Thanks.





  reply	other threads:[~2023-05-24  0:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87lehfwrzt.fsf.ref@yahoo.com>
2023-05-23  5:12 ` bug#63655: 29.0.91; Dialog box not displayed upon closing frame Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-23 11:14   ` Eli Zaretskii
2023-05-23 12:07     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-23 13:00       ` Eli Zaretskii
2023-05-23 13:16         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-23 14:48           ` Eli Zaretskii
2023-05-24  0:18             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-05-24  2:31               ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ttw2vay0.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=63655-done@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=luangruo@yahoo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.