From: Drew Adams <drew.adams@oracle.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Eli Zaretskii <eliz@gnu.org>,
"mardani29@yahoo.es" <mardani29@yahoo.es>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : Re: Q: Is there a built-in way to read multiple file names?
Date: Wed, 17 Jul 2024 19:49:37 +0000 [thread overview]
Message-ID: <SJ0PR10MB548821852AF3C7038E44E78CF3A32@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87r0bs53yx.fsf@localhost>
> >> Sure. But if multi-selection is incorporated into standard APIs,
> history
> >> may also hold the information about selected elements, in addition to
> >> minibuffer input. I do not see a reason to keep it as a completely
> >> separate structure.
> >
> > Sorry, not clear to me. Define "history of selected
> > elements".
Still not defined?
> > By "selected elements" I assume you mean something
> > like what we've been discussing: designating/marking
> > some file names (or more generally any kind of
> > completion candidates) for use as a group at some
> > time, particularly at some time other than during
> > the current act of completing patterns.
>
> Not really.
> In this thread, I am not discussing multi-selection in the completing
> read commands that are not asking for multiple answers.
> What I am interested in is extension of the UI of
> `completing-read-multiple' - when Elisp code _asks_ for one or more
> inputs.
>
> I understand that icicles is doing more than this, but I am not
> interested in icicles as is. Just in the ideas it introduces as they might
> be used in the more conventional Emacs workflows (read-multiple in
> particular)
You snipped my main message, about history,
which was to say that accessing such info via
history (e.g. M-p, M-n, M-r, M-s) is more
cumbersome than _completing_ against a set of
choices, which allows not only cycling (M-p/n)
and regexp matching (M-r/s), but additional
ways to match/access candidates directly.
Anyway, it's your enhancement project. Just
adding this comment about access via history.
___
Of course, history access can also be enhanced,
including to give access using completion.
https://www.emacswiki.org/emacs/Icicles_-_History_Enhancements
next prev parent reply other threads:[~2024-07-17 19:49 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-07 7:22 Q: Is there a built-in way to read multiple file names? Ihor Radchenko
2024-07-07 13:26 ` Daniel Martín
2024-07-07 15:56 ` Ihor Radchenko
2024-07-07 16:03 ` Eli Zaretskii
2024-07-07 17:18 ` Ihor Radchenko
2024-07-07 17:38 ` Eli Zaretskii
2024-07-07 17:47 ` Ihor Radchenko
2024-07-07 17:56 ` Eli Zaretskii
2024-07-07 21:24 ` [External] : " Drew Adams
2024-07-13 13:57 ` Ihor Radchenko
2024-07-13 18:56 ` Drew Adams
2024-07-14 12:38 ` Ihor Radchenko
2024-07-14 17:23 ` Drew Adams
2024-07-15 18:56 ` Ihor Radchenko
2024-07-15 19:44 ` Drew Adams
2024-07-17 17:21 ` Ihor Radchenko
2024-07-17 19:49 ` Drew Adams [this message]
2024-07-13 13:43 ` Ihor Radchenko
2024-07-13 13:53 ` Eli Zaretskii
2024-07-13 14:15 ` Ihor Radchenko
2024-07-13 14:28 ` Eli Zaretskii
2024-07-14 12:16 ` Ihor Radchenko
2024-07-14 13:11 ` Eli Zaretskii
2024-07-15 18:52 ` Ihor Radchenko
2024-07-15 19:22 ` Eli Zaretskii
2024-07-15 19:52 ` Ihor Radchenko
2024-07-16 10:05 ` Eli Zaretskii
2024-07-23 11:13 ` Ihor Radchenko
2024-07-23 12:05 ` Eli Zaretskii
2024-07-23 16:30 ` Ihor Radchenko
2024-07-23 16:35 ` Eli Zaretskii
2024-07-23 16:40 ` Ihor Radchenko
2024-07-23 17:48 ` Eli Zaretskii
2024-07-23 16:02 ` Yuri Khan
2024-07-23 17:35 ` [External] : " Drew Adams
2024-07-16 5:09 ` Yuri Khan
2024-07-13 14:19 ` Thierry Volpiatto
2024-07-13 14:19 ` Ihor Radchenko
2024-07-08 12:00 ` Max Nikulin
2024-07-13 14:00 ` Ihor Radchenko
2024-07-14 9:00 ` Max Nikulin
2024-07-14 12:33 ` Ihor Radchenko
2024-07-15 12:12 ` Max Nikulin
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=SJ0PR10MB548821852AF3C7038E44E78CF3A32@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mardani29@yahoo.es \
--cc=yantar92@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).