bug#64656: 29.0.91; Doc of minibuffer histories and completing-read - automatic addition of completions to DEFAULT list

[Juri Linkov]

>  But it's easy to restore it with a simple patch that prepends the
>  current default value (a command at point) to the sorted list of
>  all available command names:
>
> And even that doesn't seem to have much, if
> anything, to do with adding all of the initial
> completions to the `M-n' queue.
> So I really don't follow you, here.

All available command names mentioned above
are extracted from initial completions.

> To be very clear, I'm opposed to the misfeature
> of automatically jamming the initial completions
> onto the `M-n' queue.  We have arg DEFAULTS for
> that.  Callers of `completing-read' etc. can
> provide exactly the list of DEFAULTS they want
> to prepend to the `M-n' queue.

Indeed, ideally callers of `completing-read' should
provide the exact list of defaults.  The problem
is that it's too late to identify the existing callers
and to add an explicit list of defaults to them.

> Don't remove programmer (and user) control by
> smothering `M-n' with the completion candidates.

This doesn't remove programmer (and user) control
because it's still easy to add own default values
to `M-n' and to remove initial completions from `M-n'.