From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail
From: Spencer Baugh <sbaugh@janestreet.com>
Newsgroups: gmane.emacs.devel
Subject: Re: Updating *Completions* as you type
Date: Wed, 29 Nov 2023 10:21:47 -0500
Message-ID: <CAO=BR8OfUprMgZUSVWm5R3Kj9J7pvqRYiOwW18Q3=6SpGYOy_g@mail.gmail.com>
References: <87bkd3z9bi.fsf@catern.com> <ierleas4fcr.fsf@janestreet.com>
 <86v89ws5t3.fsf@mail.linkov.net> <iercyw445tu.fsf@janestreet.com>
 <86v89vzf1o.fsf@mail.linkov.net> <87pm03jn3w.fsf@catern.com>
 <861qcjw3ch.fsf@mail.linkov.net> <ier1qcin8db.fsf@janestreet.com>
 <86r0ki2on3.fsf@mail.linkov.net> <ierttpdlqe4.fsf@janestreet.com>
 <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>
 <CAO=BR8MUsaZ4NAZouaGxD=koonTHdkT0dCGOKryf6jf2PaNMqw@mail.gmail.com>
 <831qc87gq4.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="000000000000a10568060b4c18f4"
Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214";
	logging-data="13221"; mail-complaints-to="usenet@ciao.gmane.io"
Cc: juri@linkov.net, sbaugh@catern.com, emacs-devel@gnu.org
To: Eli Zaretskii <eliz@gnu.org>
Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Nov 29 16:54:07 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 1r8Mt4-00038Z-Uj
	for ged-emacs-devel@m.gmane-mx.org; Wed, 29 Nov 2023 16:54:07 +0100
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 1r8MsD-0008Kh-6N; Wed, 29 Nov 2023 10:53:13 -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 <sbaugh@janestreet.com>)
 id 1r8MO6-0007sh-A9
 for emacs-devel@gnu.org; Wed, 29 Nov 2023 10:22:07 -0500
Original-Received: from mxout5.mail.janestreet.com ([64.215.233.18])
 by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <sbaugh@janestreet.com>)
 id 1r8MO1-00044D-TG
 for emacs-devel@gnu.org; Wed, 29 Nov 2023 10:22:05 -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 1r8MO0-008qFS-2m for emacs-devel@gnu.org;
 Wed, 29 Nov 2023 10:21:59 -0500
Original-Received: by mail-ej1-f71.google.com with SMTP id
 a640c23a62f3a-a0dd9f85966so309194466b.1
 for <emacs-devel@gnu.org>; Wed, 29 Nov 2023 07:21:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=janestreet.com; s=google; t=1701271319; x=1701876119; 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=LSTUAsyYRy/KSWUwnnWoTsn8aq18/hmbA7LYo7Mi8m4=;
 b=x+Wi53xlfD9CH+mR0d73dXWnLjNbm1CiIhsEFulspXA3ZRSbCZI3zXb2FM2t3YaIGj
 msJXeIvdKRIKQ/IImBCwVkSKztlAXb09G3KRFqrIx35l+ItM95L0Vp/zbKmCH9BkHu5P
 K96np0Piym21KekNArqQq6LjpC1NDzDpsYMvk=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20230601; t=1701271319; x=1701876119;
 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=LSTUAsyYRy/KSWUwnnWoTsn8aq18/hmbA7LYo7Mi8m4=;
 b=SCn8sR+3PJE/f01CDrkHeO2j5V/Schz+P18bRnqGi0NUTN1A+5bO8Ke2F8xz1eZ0E4
 zOpgERGjzOtbODPjJIY9cmwR/pEEA77NTJbasRorP/6jrdQqW9M+AiM5dWd+GnuT/kY9
 rxv+H6KZLkh/q8Q0BstVED6MmKGp/Tvf/a+SksfxBxnh4dYWEXbD0XNiKKt7NPTNiBFI
 6l/pI43yNekPn9JZuAqmvpfNanWnuquDWYCs5jeQL+ANzIBixwIQz8sngHyx66y8jER+
 NZ9Ob9io2I6qTDl1lzyUWWEViyYFLJq31fDRSL09yThjSWf3NWxKsJhXAqxaORDDiOwk
 hQvg==
X-Gm-Message-State: AOJu0Yxowu574fUQApKwkmhfk9T7+k/NlRx4nFRmp5fTPmV08zfT5JeJ
 jVozjACQyuognYM8lGfDbTRbKqovPwKJ9ouoB75S/pwm4xrIVT+9fPhk1TvybyR3E/L6OYcKn80
 U16ma58PNHSVtQWa6fmffxIyrGc4=
X-Received: by 2002:a17:906:10c9:b0:a0c:c864:887c with SMTP id
 v9-20020a17090610c900b00a0cc864887cmr10672092ejv.56.1701271319141; 
 Wed, 29 Nov 2023 07:21:59 -0800 (PST)
X-Google-Smtp-Source: AGHT+IHgIYf9IVLNoxNYRDsLJ/96n4v2s9Py0UWUj3nGAu7eHfhuACFv5hEbVJS8qq0cdeNgGr0XYV7LEoH1mncErMU=
X-Received: by 2002:a17:906:10c9:b0:a0c:c864:887c with SMTP id
 v9-20020a17090610c900b00a0cc864887cmr10672076ejv.56.1701271318884; Wed, 29
 Nov 2023 07:21:58 -0800 (PST)
In-Reply-To: <831qc87gq4.fsf@gnu.org>
Received-SPF: pass client-ip=64.215.233.18; envelope-from=sbaugh@janestreet.com;
 helo=mxout5.mail.janestreet.com
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, HTML_MESSAGE=0.001,
 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 10:53:10 -0500
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:313365
Archived-At: <http://permalink.gmane.org/gmane.emacs.devel/313365>

--000000000000a10568060b4c18f4
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Nov 29, 2023 at 9:54=E2=80=AFAM Eli Zaretskii <eliz@gnu.org> wrote:

> > From: Spencer Baugh <sbaugh@janestreet.com>
> > Date: Wed, 29 Nov 2023 09:14:05 -0500
> > Cc: Juri Linkov <juri@linkov.net>, Spencer Baugh <sbaugh@catern.com>,
> emacs-devel@gnu.org
> >
> >  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".
>
> "History order" still sounds too heavy-handed.  How about "in the
> order of their typing" or somesuch?
>

Why heavy-handed?  I feel confident that more users will understand
"History order" than "in the order of their typing".

How about "Sorted in the order of minibuffer history"?

--000000000000a10568060b4c18f4
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Wed, Nov 29, 2023 at 9:54=E2=80=AFAM E=
li Zaretskii &lt;<a href=3D"mailto:eliz@gnu.org">eliz@gnu.org</a>&gt; wrote=
:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex">&gt; From: Spencer Baugh &lt;<a href=3D"mailto:sbaugh@janestre=
et.com" target=3D"_blank">sbaugh@janestreet.com</a>&gt;<br>
&gt; Date: Wed, 29 Nov 2023 09:14:05 -0500<br>
&gt; Cc: Juri Linkov &lt;<a href=3D"mailto:juri@linkov.net" target=3D"_blan=
k">juri@linkov.net</a>&gt;, Spencer Baugh &lt;<a href=3D"mailto:sbaugh@cate=
rn.com" target=3D"_blank">sbaugh@catern.com</a>&gt;, <a href=3D"mailto:emac=
s-devel@gnu.org" target=3D"_blank">emacs-devel@gnu.org</a><br>
&gt; <br>
&gt;=C2=A0 My problem with &quot;history order&quot; or &quot;historical or=
der&quot; is that it could<br>
&gt;=C2=A0 be confusing, since we are talking about input history.=C2=A0 So=
 we in fact<br>
&gt;=C2=A0 saying something like &quot;sort history in history order&quot;.=
<br>
&gt; <br>
&gt; Oh, no, this is about sorting completion candidates, not history. The =
history is still in chronological<br>
&gt; order always, it&#39;s not affected by this setting. The setting just =
determines whether completion<br>
&gt; candidates are sorted alphabetically or to match the history.<br>
&gt; <br>
&gt; So it&#39;s &quot;sort completions in history order&quot;.<br>
<br>
&quot;History order&quot; still sounds too heavy-handed.=C2=A0 How about &q=
uot;in the<br>
order of their typing&quot; or somesuch?<br></blockquote><div><br></div><di=
v>Why heavy-handed?=C2=A0 I feel confident that more users will understand =
&quot;History order&quot; than &quot;in the order of their typing&quot;.</d=
iv><div><br></div><div>How about &quot;Sorted in the order of minibuffer hi=
story&quot;?</div></div></div>

--000000000000a10568060b4c18f4--