From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Karl Fogel <kfogel@red-bean.com>
Cc: Emacs Development <emacs-devel@gnu.org>
Subject: Re: Why does `read-multiple-choice' lock user into minbuffer?
Date: Fri, 19 Jun 2020 09:43:01 +0200 [thread overview]
Message-ID: <87o8pffqm2.fsf@gmail.com> (raw)
In-Reply-To: <87r1ubfyq5.fsf@red-bean.com> (Karl Fogel's message of "Thu, 18 Jun 2020 23:47:46 -0500")
Karl Fogel <kfogel@red-bean.com> writes:
> But I'd like to understand the more general question too: why does
> `read-multiple-choice' lock the user into the minbuffer so strictly?
IIUC (but maybe I'm wrong; I'm not entirely sure I understand all the
nuances between the minibuffer and the echo-area), it's "just" an
implementation detail: read-multiple-choice uses read-event, which does
not use the minibuffer.
So you're not actually "locked into the minibuffer" (if you were, keys
such as C-x o would be available to you), it's just that
read-multiple-choice traps you in a while-loop, calling read-event until
you hit one of the keys you are prompted for.
FWIW, back in December[1] Juri mentioned that read-multiple-choice
should probably be patched to use the minibuffer.
[1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=35564#184
next prev parent reply other threads:[~2020-06-19 7:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 4:47 Why does `read-multiple-choice' lock user into minbuffer? Karl Fogel
2020-06-19 7:43 ` Kévin Le Gouguec [this message]
2020-06-19 7:44 ` Kévin Le Gouguec
2020-06-21 22:37 ` Juri Linkov
2020-06-26 9:08 ` Lars Ingebrigtsen
2020-06-26 14:35 ` T.V Raman
2020-06-26 17:57 ` Karl Fogel
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=87o8pffqm2.fsf@gmail.com \
--to=kevin.legouguec@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=kfogel@red-bean.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).