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, 29 Nov 2023 09:14:05 -0500 Message-ID: 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> <83jzq07lks.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000624079060b4b26a7" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33624"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Juri Linkov , Spencer Baugh , emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Nov 29 15:50:56 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 1r8Lts-0008Vb-Jf for ged-emacs-devel@m.gmane-mx.org; Wed, 29 Nov 2023 15:50:52 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1r8LtU-0005H8-85; Wed, 29 Nov 2023 09:50:28 -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 1r8LKW-0003Oq-JO for emacs-devel@gnu.org; Wed, 29 Nov 2023 09:14:20 -0500 Original-Received: from mxout1.mail.janestreet.com ([38.105.200.78]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1r8LKU-0007TU-LB for emacs-devel@gnu.org; Wed, 29 Nov 2023 09:14:19 -0500 Original-Received: from mail-ej1-f71.google.com ([209.85.218.71]) by mxgoog2.mail.janestreet.com with esmtps (TLS1.3:TLS_AES_128_GCM_SHA256:128) (Exim 4.96.2) id 1r8LKS-008hKw-2v for emacs-devel@gnu.org; Wed, 29 Nov 2023 09:14:15 -0500 Original-Received: by mail-ej1-f71.google.com with SMTP id a640c23a62f3a-a020d91dc93so556603066b.0 for ; Wed, 29 Nov 2023 06:14:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=janestreet.com; s=google; t=1701267255; x=1701872055; darn=gnu.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=8PDgJ9m0X/GkzyojUOZzPESNoh+/GMfxUV/RKVzAClc=; b=Ld9T4PjKafZp1iOiOwuo0b2mYy0//nERqy0Z+T+xpce0hAmEJNPjmxAm+NCmxlKyRX PgqOQO6QQXVJ2N1Gr+hWILvAsjJJprIQs+hxsae3kgUoSzx1fBjsSX/qIf6wDQ2eY8fi ifzE4GddAUVRKjD/tpe5b+/NhRmXhoEHDHbbg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701267255; x=1701872055; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=8PDgJ9m0X/GkzyojUOZzPESNoh+/GMfxUV/RKVzAClc=; b=uI1hj0gQkWAhR+TP8ASoYQ2fiP3LfHTGNPSWtopuVjRRVvnSsTpXfIfkWvXIvYGMiz Z5XUJQPQZtZ1tQ4lqcA4xwZ6JAKHWF7RT9RsCk1peZXayaR52kQwiXbE/ACDpod6erh1 1ezsmu4vCjNdzYIODpoJTZlDDdWtepSkRsuNK5zrwbo14vkTS2GmtILMpwYl/uXht386 jQq8uNflSc3aA6J2kI2zd1oZJYND7j11pnizfr6ZvLirCPV7plKgKifoZcY0QQWAo8yD RFuZMiU4RsZZHeiQ1ug89AUkrsD4KEqqPa5KMJcc9zPJ1u3jmdaUG/nVoZuXEn+jOK9u p0lQ== X-Gm-Message-State: AOJu0YxSPea4dWMwpkpDNWc+g9ceF/PLjjrOejwDvJwBI3aIvaeLZJkT AOx+ya4AvngjvihgEbGLqU90p/xkTBCBtSC57/2HPbqa1eDzjtIkRQd7Ax9MiK2Jt3K05x+no+l CRiPwGnU2egVoBq2xTb32XekxfDc= X-Received: by 2002:a17:907:d30c:b0:9bf:d65d:dc0f with SMTP id vg12-20020a170907d30c00b009bfd65ddc0fmr17966801ejc.4.1701267255048; Wed, 29 Nov 2023 06:14:15 -0800 (PST) X-Google-Smtp-Source: AGHT+IGDahVxt+32UUUViqWlPzxJOMIvUPO/ZL79MQ9KFDS/W5sLoU/BOEXfbToksIl2QVHI2z4XUiZivQVjpiYeqX4= X-Received: by 2002:a17:907:d30c:b0:9bf:d65d:dc0f with SMTP id vg12-20020a170907d30c00b009bfd65ddc0fmr17966780ejc.4.1701267254685; Wed, 29 Nov 2023 06:14:14 -0800 (PST) In-Reply-To: <83jzq07lks.fsf@gnu.org> Received-SPF: pass client-ip=38.105.200.78; envelope-from=sbaugh@janestreet.com; helo=mxout1.mail.janestreet.com X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=unavailable autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Wed, 29 Nov 2023 09:50:09 -0500 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:313363 Archived-At: --000000000000624079060b4b26a7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Nov 29, 2023, 8:10=E2=80=AFAM Eli Zaretskii wrote: > > 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". Oh, no, this is about sorting completion candidates, not history. The history is still in chronological order always, it's not affected by this setting. The setting just determines whether completion candidates are sorted alphabetically or to match the history. So it's "sort completions in history order". I'd like to > avoid using the same word twice in two different meanings, as that is > bound to confuse someone. > --000000000000624079060b4b26a7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Nov 29, 2023, 8:10=E2=80=AFAM Eli Zaretskii <eliz@gnu.org> wrote:
> From: Juri Linkov <juri@linkov.net>
> Cc: sbaugh@catern.com,=C2=A0 sbaugh@janestreet.com,=C2=A0 e= macs-devel@gnu.org
> Date: Wed, 29 Nov 2023 09:11:24 +0200
>
> >> >>=C2=A0 =C2=A0 :type '(choice (const :tag "No= sorting" nil)
> >> >>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0(const :tag "Alphabetical sorting" alphabetical)=
> >> >> +=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0(const :tag "Historical sorting" historical)
> >> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ^^^^^^^^^^^^= ^^^^^^
> >> > "Chronological sorting"
> >>
> >> Chronological sorting is how a list of buffers sorted by rece= ncy.
> >> Historical sorting is how items in history are sorted by inpu= t.
> >
> > Aren't they the same order?=C2=A0 If not, why not?
>
> "Chronological" is more wide and thus more ambiguous and con= fusing for users.

Sorry, I still don't think I follow.=C2=A0 Could you perhaps elaborate<= br> about how "chronological" is more wide?

My problem with "history order" or "historical order" i= s that it could
be confusing, since we are talking about input history.=C2=A0 So we in fact=
saying something like "sort history in history order".

Oh, no, this is= about sorting completion candidates, not history. The history is still in = chronological order always, it's not affected by this setting. The sett= ing just determines whether completion candidates are sorted alphabetically= or to match the history.

So it's "sort completions in history order".

I'd like to
avoid using the same word twice in two different meanings, as that is
bound to confuse someone.
--000000000000624079060b4b26a7--