[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Updating *Completions* as you type
From: |
Eli Zaretskii |
Subject: |
Re: Updating *Completions* as you type |
Date: |
Sun, 03 Dec 2023 19:56:42 +0200 |
> From: Juri Linkov <juri@linkov.net>
> Cc: Eli Zaretskii <eliz@gnu.org>, sbaugh@janestreet.com, emacs-devel@gnu.org
> Date: Sun, 03 Dec 2023 19:25:16 +0200
>
> > Fixed patch for everything else:
>
> No more comments in three days, so your latest patch is pushed now, thanks.
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?
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.