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: Wed, 06 Dec 2023 19:17:43 +0200 Organization: LINKOV.NET Message-ID: <86plzj9sl4.fsf@mail.linkov.net> References: <87bkd3z9bi.fsf@catern.com> <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> <86il5nhdvh.fsf@mail.linkov.net> <87plzuuend.fsf@catern.com> <837cm19ay3.fsf@gnu.org> <877cm1v3ez.fsf@catern.com> <86leab8agz.fsf@mail.linkov.net> <83bkb76ug5.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="27211"; 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: sbaugh@catern.com, sbaugh@janestreet.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Dec 06 18:29:57 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 1rAvif-0006u3-AH for ged-emacs-devel@m.gmane-mx.org; Wed, 06 Dec 2023 18:29:57 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rAvhL-0001nx-83; Wed, 06 Dec 2023 12:28:35 -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 1rAvhJ-0001ne-2M for emacs-devel@gnu.org; Wed, 06 Dec 2023 12:28:33 -0500 Original-Received: from relay9-d.mail.gandi.net ([2001:4b98:dc4:8::229]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rAvhF-0004o0-O7; Wed, 06 Dec 2023 12:28:32 -0500 Original-Received: by mail.gandi.net (Postfix) with ESMTPSA id 9FA84FF806; Wed, 6 Dec 2023 17:28:23 +0000 (UTC) In-Reply-To: <83bkb76ug5.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 03 Dec 2023 19:56:42 +0200") X-GND-Sasl: juri@linkov.net Received-SPF: pass client-ip=2001:4b98:dc4:8::229; envelope-from=juri@linkov.net; helo=relay9-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, 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:313567 Archived-At: > The NEWS entry says: > > *** New value 'historical' for user option 'completions-sort' > When 'completions-sort' is set to 'historical', completion candidates > will be sorted by their chronological order in the minibuffer history, > with more recent candidates appearing first. > > But if "more recent candidates appear first", this is not the > chronological order, this is the reverse chronological order. So > which part of the above is correct, the "chronological order" part or > the "more recent candidates first" part? In fact the word "chronological" bears no significance in this context. This feature is about the *history* variables, not some "chronological" variables. So this should be sufficient: *** New value 'historical' for user option 'completions-sort' When 'completions-sort' is set to 'historical', completion candidates will be sorted by their order in the minibuffer history, with more recent candidates appearing first. > Btw, the doc string of minibuffer-sort-by-history seems to indicate > that both the above NEWS entry and the doc string of the user options > omit crucial details: > > COMPLETIONS are sorted first by `minibuffer-sort-alphbetically', > then any elements occuring in the minibuffer history list are > moved to the front based on the chronological order they occur in > the history. > > This "alphabetical order first" part is not mentioned anywhere else. > It should at least be mentioned in the doc string of the user option > and at least hinted upon in NEWS. Agreed.