From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Spencer Baugh Newsgroups: gmane.emacs.devel Subject: Re: Updating *Completions* as you type Date: Wed, 18 Oct 2023 12:25:15 +0000 (UTC) Message-ID: <87sf68unh1.fsf@catern.com> References: <87bkd3z9bi.fsf@catern.com> <86cyxjyr1y.fsf@mail.linkov.net> <86r0lxm7um.fsf@mail.linkov.net> <87sf6dx954.fsf@catern.com> <87ttqpwea9.fsf@catern.com> <86wmvlw178.fsf@mail.linkov.net> <87bkcwx3ft.fsf@catern.com> <86y1g076vh.fsf@mail.linkov.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22716"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Juri Linkov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Oct 18 14:26:11 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 1qt5co-0005cu-LI for ged-emacs-devel@m.gmane-mx.org; Wed, 18 Oct 2023 14:26:11 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qt5c3-00084i-CZ; Wed, 18 Oct 2023 08:25:23 -0400 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 1qt5c0-000844-NX for emacs-devel@gnu.org; Wed, 18 Oct 2023 08:25:20 -0400 Original-Received: from s.wfbtzhsw.outbound-mail.sendgrid.net ([159.183.224.105]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qt5by-0007vV-NZ for emacs-devel@gnu.org; Wed, 18 Oct 2023 08:25:20 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=catern.com; h=from:subject:in-reply-to:references:mime-version:to:cc:content-type: content-transfer-encoding:cc:content-type:from:subject:to; s=s1; bh=7FA/RpSgDucae9cs7des8hR2iynu4pVOESh9NUpqlkI=; b=kF/g0jfQz5l/V7darn+BfcssLToAyIIUF4jRnVBXgcD2LzHb71O3poqWOunxV2wQxGWp Wdf5y+sQGiWykmDLrpANimlkHGMtqSyeaOtRInjx1P5FtVyTDuJUY5QLapR0RF3tKX1f2y Qz+yxxFJrufvEFoKl84DbJZy2hG6ojFJhdm5F7MgHkmRPZiIPHHsPqNMcxPb97PIujdebO bVE8XgQ5CfBNVyUX1vNGeDSUaDSG6nOFzL+1URJn3nStLwR44Yezx8Q6yXlF6fHGlrXdfY kvfSBeQlg/q3g3CjP7PZI2qugvsmk+vhJMyGjkEVbRarbUcHb+KCd2kq71mrUweA== Original-Received: by filterdrecv-655bd866f5-9wzrt with SMTP id filterdrecv-655bd866f5-9wzrt-1-652FCEAB-1E 2023-10-18 12:25:15.421335627 +0000 UTC m=+63864.835521171 Original-Received: from earth.catern.com (unknown) by geopod-ismtpd-34 (SG) with ESMTP id Rh0ohOhlQqmul2yJ9J-wcQ Wed, 18 Oct 2023 12:25:15.187 +0000 (UTC) X-Comment: SPF check N/A for local connections - client-ip=::1; helo=localhost; envelope-from=sbaugh@catern.com; receiver=linkov.net Original-Received: from localhost (localhost [IPv6:::1]) by earth.catern.com (Postfix) with ESMTPSA id 9DBEC66BD9; Wed, 18 Oct 2023 08:25:14 -0400 (EDT) In-Reply-To: <86y1g076vh.fsf@mail.linkov.net> X-SG-EID: =?us-ascii?Q?GW3oCMoYnalRiojMOuLzE6x2H5kORXvlCdz1UwQVRMVT4fbh9ODEfCogOe74cO?= =?us-ascii?Q?rI4e0V+MFZgakz9Re5a6=2FCgka9+p=2FgCc8QSWb=2FR?= =?us-ascii?Q?0xydIJpcT7qAQx1T95yJ2+B1fNzfU5ZQ3SCvrfI?= =?us-ascii?Q?1OHQMImnOvqwkliPUuiAdvoQNyNGYg39wSQ8RW=2F?= =?us-ascii?Q?=2FXbTw65+T1Vx2SUHUGrVGJR8uMjvmkgtDTZMAni?= =?us-ascii?Q?F5swMABoENGS9zxDKtehgRk46cInK8y+ipddxV?= X-Entity-ID: d/0VcHixlS0t7iB1YKCv4Q== Received-SPF: pass client-ip=159.183.224.105; envelope-from=bounces+21787432-489d-emacs-devel=gnu.org@em8926.catern.com; helo=s.wfbtzhsw.outbound-mail.sendgrid.net X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001 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:311556 Archived-At: Juri Linkov writes: >>>> Also, tangentially, I think probably we should rework >>>> minibuffer-complete-history and minibuffer-complete-defaults to be >>>> persistent - as in, regular TAB afterwards continues to complete history >>>> or defaults. And there should be some way to reset back to normal. >>>> That would be a good complement to this completions-sort change, by >>>> maybe giving a way to switch on-demand to alphabetical sorting. (I've >>>> long thought this would be good and useful, but in particular it's >>>> relevant for completions-auto-update since that will otherwise nearly >>>> immediately reset the displayed completions back to normal.) >>> >>> I think we should choose a key to toggle completion type between >>> history/default/regular completion. >> >> That works too of course, although it causes some more proliferation of >> keys. >> >> I'm curious, what is the intended usage of >> minibuffer-complete-{history,defaults}? The fact that they only do a >> single completion has made them not very usable for me. > > The currently limited use case is that you can type a substring, > then TAB and select the completion from the list. You are welcome > to improve this as well. > >>> Actually for 'C-x b' I'd prefer to sort buffers by the order of (buffer-list), >>> not by the order buffers occur in the minibuffer history (that I'd like >>> to use for everything else). >> >> Reasonable. I suggest that this should be achieved by adding a >> display-sort-function, though. (And... actually, that >> display-sort-function could maybe just be identity, since the >> completions are generated from buffer-list so they are in that order >> anyway?) > > Actually there is already a nil value in completions-sort with the tag > "No sorting". This works nicely for 'C-x b'. The remaining need is > to be able to set it only for 'C-x b', not for other completion types. I feel quite strongly that we should not extend completions-sort to be able to affect different completion types differently. Instead I think we should leave completions-sort as a blanket configuration for what to do if the completion metadata does not specify display-sort-function, and if we want to allow customizing an individual completion type, that completion type should specify a display-sort-function which can be customized. If we do extend completions-sort to affect different completion types differently, I expect we'll see lots of silly things, like packages with new completion types which automatically install changes to completions-sort instead of just specifying their own display-sort-function.