[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Why does `read-multiple-choice' lock user into minbuffer?
From: |
T.V Raman |
Subject: |
Re: Why does `read-multiple-choice' lock user into minbuffer? |
Date: |
Fri, 26 Jun 2020 07:35:01 -0700 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
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.
--