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

[Eli Zaretskii]

> Date: Mon, 16 Nov 2020 10:24:21 +0000
> From: Gregory Heytings <ghe@sdf.org>
> cc: rudalics@gmx.at, spacibba@aol.com, monnier@iro.umontreal.ca,
>         andreyk.mad@gmail.com, emacs-devel@gnu.org
> 
> > 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.

Since vertical lists and icomplete-type completion features present
the same interaction interfaces, both keyboard- and mouse-related, I
see no reason to distinguish between them in this context.

I didn't say these features should be used.  However, people do want
to use them, whether we agree or not.  When they do use such features,
I maintain that the visual appearance should be pretty and
professional, like what we see in GUI apps out there which use the
vertical list widgets.

I understand that you disagree, and that is fine.  I just don't see
why we should continue arguing long after we've established that
there's a fundamental disagreement between us.