From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: larsi@gnus.org, 52877@debbugs.gnu.org
Subject: bug#52877: [External] : Re: bug#52877: 27.2; Let `use-dialog-box' apply to more than just yes/no questions
Date: Sun, 16 Jan 2022 10:50:34 +0200 [thread overview]
Message-ID: <83bl0cysh1.fsf@gnu.org> (raw)
In-Reply-To: <SJ0PR10MB548866A7A7BE97D4EE417716F3559@SJ0PR10MB5488.namprd10.prod.outlook.com> (message from Drew Adams on Sat, 15 Jan 2022 22:12:05 +0000)
> From: Drew Adams <drew.adams@oracle.com>
> Date: Sat, 15 Jan 2022 22:12:05 +0000
> Cc: "52877@debbugs.gnu.org" <52877@debbugs.gnu.org>
>
> > So it uses a graphical chooser by default, no matter whether
> > use-dialog-box is set or not.
>
> Exactly. That's exactly the limitation this
> enhancement request asks to remove. Let _users_
> control whether it uses a graphical chooser
> or not - exactly what `use-dialog-box' is for.
>
> The limitation is that `use-dialog-box' currently
> is usable only with `yes-or-no' questions.
We don't provide any non-dialog way of selecting fonts because no one
has written code to do that. The dialog we show uses OS APIs, and the
implementation, beyond popping up the dialog and using the value it
returns, is not in Emacs.
So we simply cannot offer the users control of this, since we don't
have code to find the available fonts relevant to Emacs and display
them grouped by family, typeface, size, etc., in a useful way. We use
the system-provided dialogs instead.
IOW, this is not a bug.
next prev parent reply other threads:[~2022-01-16 8:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 17:47 bug#52877: 27.2; Let `use-dialog-box' apply to more than just yes/no questions Drew Adams
2022-01-15 10:02 ` Lars Ingebrigtsen
2022-01-15 22:12 ` bug#52877: [External] : " Drew Adams
2022-01-16 8:50 ` Eli Zaretskii [this message]
2022-01-16 22:13 ` Drew Adams
2022-01-17 12:47 ` Eli Zaretskii
2022-01-17 17:18 ` Drew Adams
2022-01-17 17:34 ` 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=83bl0cysh1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=52877@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=larsi@gnus.org \
/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).