Re: Updating *Completions* as you type

[Eli Zaretskii]

> From: Spencer Baugh <sbaugh@catern.com>
> Date: Tue, 28 Nov 2023 23:56:14 +0000 (UTC)
> Cc: juri@linkov.net, sbaugh@janestreet.com, emacs-devel@gnu.org
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> >> From: Spencer Baugh <sbaugh@catern.com>
> >> Date: Tue, 28 Nov 2023 14:38:55 +0000 (UTC)
> >> Cc: Spencer Baugh <sbaugh@janestreet.com>, emacs-devel@gnu.org
> >>    :type '(choice (const :tag "No sorting" nil)
> >>                   (const :tag "Alphabetical sorting" alphabetical)
> >> +                 (const :tag "Historical sorting" historical)
> >                                  ^^^^^^^^^^^^^^^^^^
> > "Chronological sorting"
> 
> I think "historical sorting" is more intuitive here.  "Chronological"
> seems more ambiguous - it could mean something different for files, for
> example.

I don't understand why, please explain.  Did history stop changing in
chronological order at some point and I missed that?  That is, doesn't
the first minibuffer input always precede the second one in
chronological order?