From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: VOTE: Changing completions-common-part face's default Date: Sat, 09 Nov 2019 23:57:28 +0200 Organization: LINKOV.NET Message-ID: <87pni0dctj.fsf@mail.linkov.net> References: <87h83ipoi0.fsf@gmail.com> <93235eb5-8e04-7182-e2a4-49fbe610ee2b@yandex.ru> <28d4ae09-daca-324b-2fa6-9d7138d710fa@yandex.ru> <87zhh82d8c.fsf@gmail.com> <1e1aa5a7-a35b-2ef5-6caf-10e02dd0c6ea@yandex.ru> <3cfbe69a-c274-f4f2-f3f5-9eb4c8500bb8@yandex.ru> <2f86253c-dd44-4235-9816-66bce3085fb0@default> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="258035"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (x86_64-pc-linux-gnu) Cc: emacs-devel , =?iso-8859-1?Q?Jo=E3o_T=E1vora?= , Stefan Monnier , Dmitry Gutov To: Drew Adams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Nov 09 23:08:45 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 1iTYuP-0014xU-L9 for ged-emacs-devel@m.gmane.org; Sat, 09 Nov 2019 23:08:42 +0100 Original-Received: from localhost ([::1]:40086 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iTYuO-0003Oo-HK for ged-emacs-devel@m.gmane.org; Sat, 09 Nov 2019 17:08:40 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:60873) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iTYtt-0003OL-Le for emacs-devel@gnu.org; Sat, 09 Nov 2019 17:08:10 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iTYtp-0005sr-VI for emacs-devel@gnu.org; Sat, 09 Nov 2019 17:08:09 -0500 Original-Received: from cichlid.ash.relay.mailchannels.net ([23.83.222.36]:48941) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iTYto-0005rK-Up for emacs-devel@gnu.org; Sat, 09 Nov 2019 17:08:05 -0500 X-Sender-Id: dreamhost|x-authsender|jurta@jurta.org Original-Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 16AAE501543; Sat, 9 Nov 2019 22:07:59 +0000 (UTC) Original-Received: from pdx1-sub0-mail-a35.g.dreamhost.com (100-96-14-250.trex.outbound.svc.cluster.local [100.96.14.250]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 56AA3501722; Sat, 9 Nov 2019 22:07:58 +0000 (UTC) X-Sender-Id: dreamhost|x-authsender|jurta@jurta.org Original-Received: from pdx1-sub0-mail-a35.g.dreamhost.com ([TEMPUNAVAIL]. [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.18.5); Sat, 09 Nov 2019 22:07:58 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: dreamhost|x-authsender|jurta@jurta.org X-MailChannels-Auth-Id: dreamhost X-Abortive-Chemical: 63d13ce736307fa6_1573337278803_3769641958 X-MC-Loop-Signature: 1573337278803:926252032 X-MC-Ingress-Time: 1573337278803 Original-Received: from pdx1-sub0-mail-a35.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a35.g.dreamhost.com (Postfix) with ESMTP id 12C7B7F5E6; Sat, 9 Nov 2019 14:07:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=linkov.net; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; s=linkov.net; bh=Emi1ZlhbWCrfTb/rVvXiDjUMdC4=; b= RGRmIfGEcRBlcpohYtcc+i8ep/QEOEcr22Xzyg/ffD+kJe3lxfQL4g/eetFgVpsi 21ztF8RkQhcgq2zq13zMHxgBZEU8YQGl9HP9vlvwWVv0akCwnn6ViOFMCUiN7jpe y4pKNxekDMb+m8zSo6D40lqbD4u1t+8ilpT+Cq+gx4g= Original-Received: from mail.jurta.org (m91-129-102-1.cust.tele2.ee [91.129.102.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: jurta@jurta.org) by pdx1-sub0-mail-a35.g.dreamhost.com (Postfix) with ESMTPSA id B5DDF7F249; Sat, 9 Nov 2019 14:07:48 -0800 (PST) X-DH-BACKEND: pdx1-sub0-mail-a35 In-Reply-To: <2f86253c-dd44-4235-9816-66bce3085fb0@default> (Drew Adams's message of "Fri, 8 Nov 2019 17:53:51 -0800 (PST)") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 23.83.222.36 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:242057 Archived-At: >> > That would still mean two diffeerent execution flows. >> >> Don't know what you mean exactly. But yes, I guess. When >> using prefix I am focused on one thing, when using flex I am >> focused on another thing. I think that already happens anyway >> (the internal focus of the user). >> >> But I don't use prefix much nowadays, fortunately. The beginning >> of a name has no special place in my mind. >> >> But Juri has given as an example a search box that does >> exactly this mixing _in the same search results_. > > I haven't really followed all of the messages, > and I'm not sure what is meant here, by "mixing > completion styles in the same search results". Chromium mixes different completion styles in one completion list, for example: https://www.chromestory.com/2018/05/omnibox-redesign/ It highlights completion matches using bold that works also for blue links (e.g. "nytimes.com" in the example above). I'm not sure what completion style supports listing links in the *Completions* buffer, but using blue for links and blue for matches will make them indistinguishable from each other in the *Completions* buffer. If changing the defaults is so highly sensitive topic, I don't see what would be wrong with adding a new face inheriting from completions-first-difference and applying only to flex-like completion styles. No change in defaults will maintain the status quo. Another advantage of adding a new face is that anyone can customize flex highlighting without affecting the faces of the prefix completion style.