From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail
From: Juri Linkov <juri@linkov.net>
Newsgroups: gmane.emacs.devel
Subject: Re: Updating *Completions* as you type
Date: Wed, 18 Oct 2023 09:56:02 +0300
Organization: LINKOV.NET
Message-ID: <86y1g076vh.fsf@mail.linkov.net>
References: <87bkd3z9bi.fsf@catern.com> <86cyxjyr1y.fsf@mail.linkov.net>
 <ier34ye4a3x.fsf@janestreet.com> <86r0lxm7um.fsf@mail.linkov.net>
 <87sf6dx954.fsf@catern.com> <87ttqpwea9.fsf@catern.com>
 <86wmvlw178.fsf@mail.linkov.net> <87bkcwx3ft.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="9773"; 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: emacs-devel@gnu.org
To: Spencer Baugh <sbaugh@catern.com>
Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Oct 18 09:04:05 2023
Return-path: <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>
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 <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>)
	id 1qt0b5-0002MG-MC
	for ged-emacs-devel@m.gmane-mx.org; Wed, 18 Oct 2023 09:04:03 +0200
Original-Received: from localhost ([::1] helo=lists1p.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.90_1)
	(envelope-from <emacs-devel-bounces@gnu.org>)
	id 1qt0a8-0001fl-FY; Wed, 18 Oct 2023 03:03:04 -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 <juri@linkov.net>) id 1qt0a6-0001fY-UG
 for emacs-devel@gnu.org; Wed, 18 Oct 2023 03:03:03 -0400
Original-Received: from relay5-d.mail.gandi.net ([2001:4b98:dc4:8::225])
 by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <juri@linkov.net>) id 1qt0a5-0005fm-3F
 for emacs-devel@gnu.org; Wed, 18 Oct 2023 03:03:02 -0400
Original-Received: by mail.gandi.net (Postfix) with ESMTPSA id 77A801C000A;
 Wed, 18 Oct 2023 07:02:56 +0000 (UTC)
In-Reply-To: <87bkcwx3ft.fsf@catern.com> (Spencer Baugh's message of "Tue, 17
 Oct 2023 22:57:27 +0000 (UTC)")
X-GND-Sasl: juri@linkov.net
Received-SPF: pass client-ip=2001:4b98:dc4:8::225;
 envelope-from=juri@linkov.net; helo=relay5-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,
 SPF_HELO_PASS=-0.001, SPF_PASS=-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." <emacs-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-devel>,
 <mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/emacs-devel>
List-Post: <mailto:emacs-devel@gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-devel>,
 <mailto:emacs-devel-request@gnu.org?subject=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:311555
Archived-At: <http://permalink.gmane.org/gmane.emacs.devel/311555>

>>> 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.