Re: [PATCH] `completing-read`: Add `group-function` support to completion metadata

[Stefan Monnier]

>> I was thinking only of tweaking the existing UI to better support the
>> case of "selection" compared to "completion".  What you suggest here is
>> nice and it goes much further but I don't think the two are competing.
>
> Perhaps a "selection" tweak on the *Completions* interface could look like
> this:
>
> When completing-read is called (or selecting-read, IDK), *Completions*
> buffer is popped up. The first element in the list is highlighted with some
> noticeable background, thus telling the user that if they press RET right
> away, that item will be selected. The user can now type some characters to
> narrow down the matches, or the can move the selection along the list with,
> say, arrow keys. Or C-n/C-p. Or press RET right away to choose the first
> completion. Not sure if iteration with TAB is a good idea, but it could be
> added as well.

Yes, that's pretty much the UI behavior I imagine.

> That doesn't solve the issue of hiding a "useful" window with this buffer,
> but there's probably not much that can be done.

Normally we should already try and make efforts not to hide "obviously
useful" text when we pop up *Completions*, and as for the part that
aren't obviously useful (or that we can't not hide) the user can always
go and hide the *Completions* buffer manually (or do any other normal
window manipulation).


        Stefan