From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 63655@debbugs.gnu.org
Subject: bug#63655: 29.0.91; Dialog box not displayed upon closing frame
Date: Wed, 24 May 2023 05:31:33 +0300 [thread overview]
Message-ID: <83pm6qo3y2.fsf@gnu.org> (raw)
In-Reply-To: <87ttw2vay0.fsf@yahoo.com> (message from Po Lu on Wed, 24 May 2023 08:18:31 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: 63655-done@debbugs.gnu.org
> Date: Wed, 24 May 2023 08:18:31 +0800
>
> 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.
I understand, but I think we are fine with the change on emacs-29. If
I'm wrong, we'd know soon enough.
prev parent reply other threads:[~2023-05-24 2:31 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
2023-05-24 2:31 ` Eli Zaretskii [this message]
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=83pm6qo3y2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=63655@debbugs.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.