Re: Navigating completions from minibuffer

[Spencer Baugh]

Juri Linkov <juri@linkov.net> writes:
>> Maybe we can deselect by moving point to just before (or after) the
>> selected candidate?  Move point to the whitespace in-between candidates.
>> Then no candidate is selected, and completions-highlight-face won't
>> highlight any candidate, but there's still a bit of visual indicator
>> (window-point) which shows what candidate was previously selected, and
>> if the user does want to re-select the candidate, the user can just hit
>> <down> (or <up>) to select the candidate again.
>
> In fact, the whitespace in-between candidates is the only place where
> point could be moved to deselect the candidate.  Because there is no space
> at the end of the completions buffer, and even at the beginning when
> both completion-show-help and completions-header-format are nil.

Oh, great!  So then let's just do that.

Possibly we should ensure there is one character worth of whitespace at
the end of the completions buffer, so we can consistently just move
point to right after the selected candidate to deselect it.


Also... doesn't this mean that with

(setq completion-show-help nil
      completions-header-format nil)

*Completions* will start out with the point on the first completion
candidate?  So M-RET will select it, and with
minibuffer-visible-completions=t, even RET will select it?

Maybe point should uniformly start at the end of *Completions* instead
of at the start?  In the one character worth of whitespace we might add?