From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: Updating *Completions* as you type Date: Mon, 27 Nov 2023 09:28:50 +0200 Organization: LINKOV.NET Message-ID: <86il5nhdvh.fsf@mail.linkov.net> References: <87bkd3z9bi.fsf@catern.com> <875y33v73h.fsf@catern.com> <87y1fztke8.fsf@catern.com> <86r0lrw17x.fsf@mail.linkov.net> <87il5xlf9b.fsf@catern.com> <86y1esuajx.fsf@mail.linkov.net> <86v89ws5t3.fsf@mail.linkov.net> <86v89vzf1o.fsf@mail.linkov.net> <87pm03jn3w.fsf@catern.com> <861qcjw3ch.fsf@mail.linkov.net> <86r0ki2on3.fsf@mail.linkov.net> <86leao519y.fsf@mail.linkov.net> <87fs0wk5oq.fsf@catern.com> <86edgfin4v.fsf@mail.linkov.net> <87o7fhixzv.fsf@catern.com> <86o7fhy9ae.fsf@mail.linkov.net> <87v89ohc6f.fsf@catern.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33435"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/30.0.50 (x86_64-pc-linux-gnu) Cc: Spencer Baugh , emacs-devel@gnu.org To: sbaugh@catern.com Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Nov 27 08:33:17 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1r7W7I-0008YU-42 for ged-emacs-devel@m.gmane-mx.org; Mon, 27 Nov 2023 08:33:16 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1r7W6L-0003bp-BK; Mon, 27 Nov 2023 02:32:18 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1r7W6F-0003at-9O for emacs-devel@gnu.org; Mon, 27 Nov 2023 02:32:11 -0500 Original-Received: from relay8-d.mail.gandi.net ([217.70.183.201]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1r7W6B-0002v6-6B for emacs-devel@gnu.org; Mon, 27 Nov 2023 02:32:10 -0500 Original-Received: by mail.gandi.net (Postfix) with ESMTPSA id 9594F1BF209; Mon, 27 Nov 2023 07:32:04 +0000 (UTC) In-Reply-To: <87v89ohc6f.fsf@catern.com> (sbaugh@catern.com's message of "Sun, 26 Nov 2023 13:33:45 +0000 (UTC)") X-GND-Sasl: juri@linkov.net Received-SPF: pass client-ip=217.70.183.201; envelope-from=juri@linkov.net; helo=relay8-d.mail.gandi.net X-Spam_score_int: -25 X-Spam_score: -2.6 X-Spam_bar: -- X-Spam_report: (-2.6 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:313263 Archived-At: >> This is what I believe they should do: we add a category, >> and they support it as well. > > OK, I'm fine with that, but when we do that, I think the per-table > option should override the per-category option. I agree that the per-table option should override the per-category option, but see no way to distinguish customized values from hard-coded ones without trying to turn all hard-coded values into options. display-buffer has a similar problem, but the difference is that it's possible to identify a buffer by its name and use a regexp to match buffer names. Whereas for completing-read it's not easy to identify a completion table. A category matches a set of completion tables, so maybe we need another identification for individual tables? > I'm OK with a category-based approach. I just think we should reserve > the *ability* to use table-specific options, by making a table-specific > display-sort-function override the category-specific display-sort-function. Probably introducing a new field to metadata could help to resolve ambiguities. > Anyway, we're going around in circles a bit here. How about this patch > which only adds the new historical option to completions-sort? I think > we're in agreement on everything in this patch, and maybe installing it > will get some user feedback which we can use when coming back to this > later. Thanks, everything looks nice, only a etc/NEWS announcement is missing.