Re: Updating *Completions* as you type

[Juri Linkov]

> 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?

In fact the word "chronological" bears no significance in this context.
This feature is about the *history* variables, not some "chronological"
variables.  So this should be sufficient:

    *** New value 'historical' for user option 'completions-sort'
    When 'completions-sort' is set to 'historical', completion candidates
    will be sorted by their order in the minibuffer history,
    with more recent candidates appearing first.

> 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.

Agreed.