unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Karl Fogel <kfogel@red-bean.com>
To: "T.V Raman" <raman@google.com>
Cc: "Lars Ingebrigtsen" <larsi@gnus.org>,
	"Emacs Development" <emacs-devel@gnu.org>,
	"Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Subject: Re: Why does `read-multiple-choice' lock user into minbuffer?
Date: Fri, 26 Jun 2020 12:57:28 -0500	[thread overview]
Message-ID: <87eeq1n20n.fsf@red-bean.com> (raw)
In-Reply-To: <p91d05lzyi2.fsf@google.com> (T. V. Raman's message of "Fri, 26 Jun 2020 07:35:01 -0700")

On 26 Jun 2020, T.V Raman wrote:
>Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>The other function that demonstrates the same issue is read-char-choice
>and clients that use it --e.g. magit et al then are forced to put up
>hard to parse prompts of the form [u]rl, [n]ame, ... as an
>example. Another good example of a hard to use client UI is org's export
>wizard.
>
>Note: If you can see the screen, prompts like the above work once you're
>familiar with them, with spoken output, they're a complete usability disaster.
>--
>> Kévin Le Gouguec <kevin.legouguec@gmail.com> writes:
>>
>>> FWIW, back in December[1] Juri mentioned that read-multiple-choice
>>> should probably be patched to use the minibuffer.
>>
>> Yup, I agree.

Thanks, everyone.  I will try to find time to do something on this this weekend.  I'll post a patch in this thread for review before committing anything, as (I suspect) this is an unfamiliar area of the code for me.

Best regards,
-Karl



      reply	other threads:[~2020-06-26 17:57 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
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 [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

  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=87eeq1n20n.fsf@red-bean.com \
    --to=kfogel@red-bean.com \
    --cc=emacs-devel@gnu.org \
    --cc=kevin.legouguec@gmail.com \
    --cc=larsi@gnus.org \
    --cc=raman@google.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).