RE: [External] : Re: Q: Is there a built-in way to read multiple file names?

[Ihor Radchenko <yantar92@posteo.net>]

Drew Adams <drew.adams@oracle.com> writes:

>> 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".
>
> 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)

-- 
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>