From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: paaguti@gmail.com, emacs-devel@gnu.org
Subject: Re: Change to `use-dialog-box-p'
Date: Mon, 22 May 2023 14:28:03 +0300 [thread overview]
Message-ID: <83y1lgppvg.fsf@gnu.org> (raw)
In-Reply-To: <87353ozpfm.fsf@yahoo.com> (message from Po Lu on Mon, 22 May 2023 17:27:25 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: emacs-devel@gnu.org, eliz@gnu.org
> Date: Mon, 22 May 2023 17:27:25 +0800
>
> Pedro A. Aranda Gutiérrez <paaguti@gmail.com> writes:
>
> > Eli writes,
> >
> >> It's not a "behavior", it's a bug! The behavior we will get with the
> >> change you suggest will surprise (and annoy) many more users!
>
> But we've had this old behavior for decades without complaints.
The situation you are talking about almost never happens, because
last-nonmenu-event is almost never nil. So the lack of complaints
does not surprise me.
And you haven't answered my question:
> Btw, use-dialog-box-p also looks at last-input-event, and only pops up
> a dialog box if that is non-nil. In your scenario, is
> last-input-event non-nil? If so, what is it, and where did it come
> from?
Please answer this, I think there's some factor here we need to
understand. Right after startup, last-input-event should be nil.
next prev parent reply other threads:[~2023-05-22 11:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 5:33 Re: Change to `use-dialog-box-p' Pedro A. Aranda Gutiérrez
2023-05-22 9:27 ` Po Lu
2023-05-22 10:17 ` Pedro Andres Aranda Gutierrez
2023-05-22 11:28 ` Eli Zaretskii [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-23 1:39 Samuel Wales
2023-05-23 11:35 ` Eli Zaretskii
[not found] <87o7mf3em6.fsf.ref@yahoo.com>
2023-05-20 2:45 ` Po Lu
2023-05-20 5:56 ` Eli Zaretskii
2023-05-20 6:29 ` Po Lu
2023-05-20 8:14 ` Eli Zaretskii
2023-05-20 8:32 ` Po Lu
2023-05-20 9:41 ` Eli Zaretskii
2023-05-20 11:17 ` Po Lu
2023-05-20 12:38 ` Eli Zaretskii
2023-05-21 0:47 ` Po Lu
2023-05-21 5:50 ` Eli Zaretskii
2023-05-21 6:41 ` Po Lu
2023-05-21 7:40 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83y1lgppvg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=paaguti@gmail.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).