From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: =?UTF-8?B?Sm/Do28gVMOhdm9yYQ==?= Newsgroups: gmane.emacs.devel Subject: Re: BIKESHED: completion faces Date: Mon, 28 Oct 2019 23:31:27 +0000 Message-ID: References: <87ftjd6gbu.fsf@mail.linkov.net> <87blu18zsg.fsf@gmail.com> <87sgncqydt.fsf@mail.linkov.net> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000b7c4ab059600e6c5" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="81782"; mail-complaints-to="usenet@blaine.gmane.org" Cc: Stefan Monnier , emacs-devel To: Juri Linkov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 29 00:32:21 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iPEUn-000L9l-Dj for ged-emacs-devel@m.gmane.org; Tue, 29 Oct 2019 00:32:21 +0100 Original-Received: from localhost ([::1]:45442 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iPEUl-0003kA-Pz for ged-emacs-devel@m.gmane.org; Mon, 28 Oct 2019 19:32:19 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57559) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iPEU9-0003fo-3m for emacs-devel@gnu.org; Mon, 28 Oct 2019 19:31:42 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iPEU7-0006fM-Lq for emacs-devel@gnu.org; Mon, 28 Oct 2019 19:31:40 -0400 Original-Received: from mail-io1-xd2e.google.com ([2607:f8b0:4864:20::d2e]:38195) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iPEU7-0006fA-HI for emacs-devel@gnu.org; Mon, 28 Oct 2019 19:31:39 -0400 Original-Received: by mail-io1-xd2e.google.com with SMTP id u8so12704222iom.5 for ; Mon, 28 Oct 2019 16:31:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jSn/PrfF9iMZgUR8QZ6SitP8n0XhfKOoJlffkm4OWPs=; b=qN+2SjTmOTWjmig4xwFAU6OnZ41lKF6XaX/QIzoXvifNcQYkAhwHbyOBJgxTZMjn73 iacaBabUj3Wt1Kp+0zDQJpCoGlyczwV3mbhON2NhCZDR05eAXqOqLeIExjy4Lm2nmvvm PYlYTNDdYo0EeqtSEPRfobEw7iqD/yBtpeaaKxqWZPt2wMBWszs3jevant+i0QA+UBJf uNGns92xwA3/BNodb/fxpepRkcPj3Vhi5qtsI7/9nxGwe4UCZ55/yi7EyyGk/A0UCv7k TTnkYtwWAxZRQvXMD+cFRqyVYQJWhHNnoyk+edeNKS4xcd3JUL/iAscmq4q3TgWYBQcu bChA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=jSn/PrfF9iMZgUR8QZ6SitP8n0XhfKOoJlffkm4OWPs=; b=Su3eGQ7Du94EytbYx3DO0dBkUw4JgdrjEUUxg9lfq8Jrr00Ez6DFis5LrwidOOFE9B gEeb+Gp+Jc2ZLN+QkQduLxiRG28FR19Ko6qLLwCyK/p1WglI/q8p16jbYu7cV+cr1SLA tntuS0gliC7kHZPVM+TPepk88LA/+/SKia3S/eSNDYd5+xPsVgDg2GUhlECOOciFwIrm JPzJR3GiXe9y93DyOOB3lMMP43FGKlKHXf2yNJMF5CTDCtbV/axA7UHP13c2EAHbhgr8 3UKiI48yIlsh5r8PYU0z1hPcZSuIh3Bjbd3ioYkYKzQJaBNscqs2Tqp8oszkLAy5wiYn DMng== X-Gm-Message-State: APjAAAVIvzGedCl/N7pMQ13n9/rhRuYEka1x55FM0EDNBssfIMxunWUA cyUFYt/ktI0XowpVJcIo+98syZJVpT72Afmy96o= X-Google-Smtp-Source: APXvYqxSv23KF9HE8gExwv3BhFQDjJ5TeN3ySdlJ2f0z084eNXkun9df0G8NjeDyFKus2RfjGIE8sNwBFCeT0thqTeI= X-Received: by 2002:a6b:b2d5:: with SMTP id b204mr596838iof.137.1572305498520; Mon, 28 Oct 2019 16:31:38 -0700 (PDT) In-Reply-To: <87sgncqydt.fsf@mail.linkov.net> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:4864:20::d2e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:241568 Archived-At: --000000000000b7c4ab059600e6c5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Oct 28, 2019 at 11:01 PM Juri Linkov wrote: > > >> bold in completions-first-difference helps to immediately see the > >> next character to type to narrow completions further. > > > > > > > > Yes, but some questions, Juri: > > > > * wouldn't any other face, say "underline", serve the same purpose? > > underline is less noticeable than bold, when used on a single character > with completions-first-difference in the "basic" completion style. > > * would you not be equally and efficiently informed of such facts if > > completions-common-part were _more_ prominent and > > completions-first-difference was _less_ prominent? > > In the "basic" completion style completions-first-difference > needs to be more prominent since it's more important to indicate > the next character to type. I understand. But if completion-common-part is super-prominent, you get more or less the same, right? It's also very easy to see the "next" character to type. > Other completion styles don't highlight completions-first-difference > at all. I'm not sure if only the "basic" completion style highlights > completions-first-difference. Eh. I removed it recently, without asking anyone, waiting for someone to complain. :-) Are you complaining? :-) If you are, I'll revert that bit. If you aren't I probably should revert it too... Anyway, I don't think it makes a lot of sense in those styles, unless you are editing inside the completion string, which is relatively rare. > Is it possible to use bold for completions-first-difference only > in the "basic" completion style, but for other completion styles > to use bold for completions-common-part? That would make some sense, yes. Perhaps we just need better names for the faces. Perhaps a new alias "completion-important-bits-for-style" for the current completion-first-difference would do fine. We probably need a better name, tho... "completion-style-hint"? "completion-emphasis"? Jo=C3=A3o --000000000000b7c4ab059600e6c5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, Oct 28, 2019 at 11:01 PM Juri Linkov <juri@linkov.net> wrote:
>
> = >> bold in completions-first-difference helps to immediately see the<= br>> >> next character to type to narrow completions further.
&= gt; >
> > <mild bikeshedding starts>
> >
>= > Yes, but some questions, Juri:
> >
> > * wouldn'= ;t any other face, say "underline", serve the same purpose?
&g= t;
> underline is less noticeable than bold, when used on a single ch= aracter
> with completions-first-difference in the "basic&q= uot; completion style.

> > * would you not be equ= ally and efficiently informed of such facts if
> > =C2=A0 completi= ons-common-part were _more_ prominent and
> > =C2=A0 completions-f= irst-difference was _less_ prominent?
>
> In the "basic&qu= ot; completion style completions-first-difference
> needs to be more = prominent since it's more important to indicate
> the next c= haracter to type.

I understand. But if completion-= common-part is super-prominent, you get
more or less the same, ri= ght?=C2=A0 It's also very easy to see the "next" character
to type.

> Other completion styles = don't highlight completions-first-difference
> at all.=C2=A0 I&= #39;m not sure if only the "basic" completion style highlights
> completions-first-difference.

Eh.=C2=A0= I removed it recently, without asking anyone, waiting for
someon= e to complain. :-)

Are you complaining? :-)=C2=A0 = If you are, I'll revert that bit. If you aren't
I probabl= y should revert it too...

Anyway, I don't = think it makes a lot of sense in those styles,
unless you ar= e editing inside the completion string,
which is relatively rare.=

> Is it possible to use bold for completions-first-= difference only
> in the "basic" completion style, but for = other completion styles
> to use bold for completions-common-par= t?

That would make some sense, yes.=C2=A0 Perhaps = we just need better names
for the faces. Perhaps a new alias &quo= t;completion-important-bits-for-style"
for the current compl= etion-first-difference would do fine.=C2=A0 We probably
need= a better name, tho... "completion-style-hint"? "completion-= emphasis"?

Jo=C3=A3o
--000000000000b7c4ab059600e6c5--