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

[Eli Zaretskii]

> Date: Wed, 11 Nov 2020 18:39:41 +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
> 
> I honestly don't understand why you consider that vertical icomplete is 
> "not pretty", even more so as you seem to consider at the same time that 
> Emacs' handling of emails and web pages is okay.  IMO, Emacs' rendering of 
> HTML in emails and on web pages is definitely not pretty.  IMO again, 
> displaying completion candidates in the minibuffer is pretty enough, at 
> least I don't see why it would be fundamentally less pretty for a newcomer 
> than, say, the completion candidates displayed by Chromium or Visual 
> Studio.

If someone wants to claim that display of completion candidates by
icomplete-vertical, ivy, etc. is anywhere near as pretty as what you
get when you click on the address bar of a browser and get the
drop-down list of candidates, then I can only say that I cannot
disagree more.

> > If you read the code that is involved, the reasons are acutely evident, 
> > and it is important for me to make these conclusions public and known to 
> > all, because many people believe there's no limit to what one can do 
> > with Emacs display features. Well, there is.
> 
> There are limits, of course, but the feature that is requested is well 
> within the limits of what Emacs can do.  And AFAIU implementing a proper 
> vertical icomplete/ido with a few more features similar to those of Ivy is 
> also within the limits of what Emacs can do.

I explicitly said that Emacs _can_ do that.  My point was entirely
different.