Re: [PATCH] Support "\n" in icomplete-separator

[Gregory Heytings]

> > > No, I mean what would happen if we displayed a menu simulation by 
> > > showing menu items one below the other in a buffer, instead of using 
> > > the toolkit menus, or even instead of the TTY menus we have nowadays.
> >
> > Okay, now I see what you mean.  Indeed doing this for menus would not 
> > make sense / would be ugly.  But of course the essential difference 
> > here is that menus are not meant to be used with a keyboard
>
> Actually, menus (even GUI toolkit menus) work with the keyboard very 
> well.  Including in Emacs.  It's true that interaction with GUI widgets, 
> including the vertical lists, quite naturally is biased towards pointing 
> devices, but it is not limited to them.
>
> The important difference, at least for the purposes of this discussion, 
> is what menus look like, not how users interact with them.

What I said was probably not clear enough.

My argument is the following: as you said, GUI widgets such as menus and 
vertical list widgets are "biased towards pointing devices".

Therefore GUI widgets such as menus and vertical list widgets should not 
be used where the primary interaction device is the keyboard.

Therefore vertical list widgets should not be used to display completion 
candidates in the minibuffer, where the primary interaction device is the 
keyboard.