From: Ihor Radchenko <yantar92@posteo.net>
To: Rahguzar <rahguzar@zohomail.eu>
Cc: Thierry Volpiatto <thievol@posteo.net>,
Eli Zaretskii <eliz@gnu.org>,
mardani29@yahoo.es, emacs-devel@gnu.org
Subject: Alternative UI for reading multiple choices (was: Q: Is there a built-in way to read multiple file names?)
Date: Mon, 15 Jul 2024 19:09:21 +0000 [thread overview]
Message-ID: <87jzhmiiam.fsf@localhost> (raw)
In-Reply-To: <87ikx7ra2i.fsf@zohomail.eu>
Rahguzar <rahguzar@zohomail.eu> writes:
>> The main problem is that it is not built-in, and I would like to get
>> something in the core to cater multi-file prompts.
>
> I would like that too, and if something like that is in the core I will
> change current implementation to depend on it. I am also happy to try to
> upstream the code if that is considered desirable.
Let's change the subject then.
Eli favours a completely different approach for selecting files in
particular, but improving `completing-read-multiple' is also worth
discussing:
- Built-in `completing-read-multiple' works fine using its idea with
separators, but it is a pain to remove previously selected choices,
especially long and complex ones.
- filechooser implements an alternative way to read multiple choices by
showing them as additional completion group on top of the normal
completions
- This is conceptually similar to icicles, except that the highlights in
icicles may work not as good when the number of completion candidates
is too large. I feel that visual indication in a separate group is
better, except when all possible completions can fit within
*completions* buffer window
- As we discussed with Drew, the problem with not having all the
completions listed in the minibuffer (like in
`completing-read-multiple') is that it does not get stored in the
minibuffer history. And it would be nice to have access to such
history for multiple choice prompt.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-07-15 19:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-13 16:28 Q: Is there a built-in way to read multiple file names? Rahguzar
2024-07-14 12:30 ` Ihor Radchenko
2024-07-14 20:29 ` Rahguzar
2024-07-15 19:09 ` Ihor Radchenko [this message]
2024-07-15 20:02 ` [External] : Alternative UI for reading multiple choices (was: Q: Is there a built-in way to read multiple file names?) Drew Adams
2024-07-15 19:12 ` ELPA package: filechooser " Ihor Radchenko
2024-07-16 8:59 ` ELPA package: filechooser Rahguzar
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=87jzhmiiam.fsf@localhost \
--to=yantar92@posteo.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mardani29@yahoo.es \
--cc=rahguzar@zohomail.eu \
--cc=thievol@posteo.net \
/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).