From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Updating *Completions* as you type Date: Wed, 29 Nov 2023 15:09:23 +0200 Message-ID: <83jzq07lks.fsf@gnu.org> 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> <86jzq1kh7m.fsf@mail.linkov.net> <831qc993vg.fsf@gnu.org> <86jzq1t623.fsf@mail.linkov.net> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="32919"; mail-complaints-to="usenet@ciao.gmane.io" Cc: sbaugh@catern.com, sbaugh@janestreet.com, emacs-devel@gnu.org To: Juri Linkov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Nov 29 14:10:45 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 1r8KKz-0008LG-5y for ged-emacs-devel@m.gmane-mx.org; Wed, 29 Nov 2023 14:10:45 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1r8KJu-0002UO-Iy; Wed, 29 Nov 2023 08:09:38 -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 1r8KJs-0002Tz-6d for emacs-devel@gnu.org; Wed, 29 Nov 2023 08:09:37 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1r8KJq-0001r5-Vd; Wed, 29 Nov 2023 08:09:34 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=UFhGSKrj7nBCf3mDIXw26Uqxrlhjkz2yeHz7BUV1W90=; b=DkLLU0IhDSCi I3q81q6bBpTD89K41LKgiyHmRewtrLtI0klMDpr0vYYFRmi62hb3QXMPGlM78Q9vz7vRWI2xGmCTw k2wCmhFrV3fV85IDPNj8SnAhzxcrHIz/l1Tg2Tqobeo2M9tcsRy+iMACKXE0jqLQ4Kw5jyikK+LQo DMdwIBHnw5GFb8LT1YgpfYjBqHeDYVG9UISHW/TsZYS4uu9wfm3zj1nTVq/qUxbWOCi4pFiBF6CTh IVJd1RZpGIDica0hTiN5jRhg8Bh8UqPtIBDhleG091BulZw75NKI6F4xBN7drxsb11rbwgM3izlMP gTDo0iIIoblgTy2mAgrsxg==; In-Reply-To: <86jzq1t623.fsf@mail.linkov.net> (message from Juri Linkov on Wed, 29 Nov 2023 09:11:24 +0200) 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:313358 Archived-At: > From: Juri Linkov > Cc: sbaugh@catern.com, sbaugh@janestreet.com, emacs-devel@gnu.org > Date: Wed, 29 Nov 2023 09:11:24 +0200 > > >> >> :type '(choice (const :tag "No sorting" nil) > >> >> (const :tag "Alphabetical sorting" alphabetical) > >> >> + (const :tag "Historical sorting" historical) > >> > ^^^^^^^^^^^^^^^^^^ > >> > "Chronological sorting" > >> > >> Chronological sorting is how a list of buffers sorted by recency. > >> Historical sorting is how items in history are sorted by input. > > > > Aren't they the same order? If not, why not? > > "Chronological" is more wide and thus more ambiguous and confusing for users. Sorry, I still don't think I follow. Could you perhaps elaborate about how "chronological" is more wide? My problem with "history order" or "historical order" is that it could be confusing, since we are talking about input history. So we in fact saying something like "sort history in history order". I'd like to avoid using the same word twice in two different meanings, as that is bound to confuse someone.