unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: Change to `use-dialog-box-p'
Date: Sat, 20 May 2023 11:14:26 +0300	[thread overview]
Message-ID: <83wn13s9lp.fsf@gnu.org> (raw)
In-Reply-To: <87jzx33487.fsf@yahoo.com> (message from Po Lu on Sat, 20 May 2023 14:29:44 +0800)

> From: Po Lu <luangruo@yahoo.com>
> Cc: emacs-devel@gnu.org
> Date: Sat, 20 May 2023 14:29:44 +0800
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Because last-nonmenu-event being nil happens in too many cases where
> > showing the GUI dialog is not TRT.  Immediately after startup, for
> > example.
> >
> > What is the situation where you need to show a GUI dialog even though
> > last-nonmenu-event is nil?
> 
> Precisely this one: immediately after start up.  I don't understand why
> it's not correct to show a dialog box in that situation; in many cases,
> it's much easier to use the dialog box than to use the keyboard.

Can you show a specific recipe where this happens?  Otherwise it is
hard to reason about the issue.

AFAIR, without that change, just invoking y-or-n-p after startup would
show a GUI dialog, and that doesn't sound right to me.

IME, showing GUI dialogs by default is not TRT, because Emacs
generally defaults to keyboard input via the minibuffer, and only
shows the GUI dialog when the command was invoked via a mouse or from
a menu.  In other cases we don't force users to use the mouse for
Emacs interaction.



  reply	other threads:[~2023-05-20  8:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87o7mf3em6.fsf.ref@yahoo.com>
2023-05-20  2:45 ` Change to `use-dialog-box-p' Po Lu
2023-05-20  5:56   ` Eli Zaretskii
2023-05-20  6:29     ` Po Lu
2023-05-20  8:14       ` Eli Zaretskii [this message]
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
2023-05-22  5:33 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
  -- strict thread matches above, loose matches on Subject: below --
2023-05-23  1:39 Samuel Wales
2023-05-23 11:35 ` 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=83wn13s9lp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@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 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).