The @code{completions-sort} user option controls the order in which
the completions are sorted in the @samp{*Completions*} buffer. The
default is @code{alphabetical}, which sorts in alphabetical order.
-The value @code{nil} disables sorting. The value can also be a
-function, which will be called with the list of completions, and
-should return the list in the desired order.
+The value @code{historical} sorts completion candidates according to
+their position in the minibuffer history, so candidates that you used
+recently appear first in the completions list. The value @code{nil}
+disables sorting altogether. The value can also be a function, which
+will be called with the list of completions, and should return the
+list in the desired order.
@vindex completions-max-height
When @code{completions-max-height} is non-@code{nil}, it limits the
controlled with the new user option 'completion-auto-deselect', which
is t by default.
++++
*** New value 'historical' for user option 'completions-sort'.
When 'completions-sort' is set to 'historical', completion candidates
will be first sorted alphabetically, and then re-sorted by their order
in the minibuffer history, with more recent candidates appearing first.
++++
*** New commands for narrowing (restricting) minibuffer completions list.
You can now use 'C-x n n' ('minibuffer-narrow-completions-to-current')
in the minibuffer to restrict the list of possible completions to only