Re: switch-to-completions

[Stefan Monnier <monnier@iro.umontreal.ca>]

> I'm not sure what function should take care about finding the right place
> since creation of the *Completions* buffer is shared among several functions:
> `display-completion-list' inserts the text "Possible completions are:\n",
> `completion-setup-function' inserts the help text with one newline or
> two newlines depending on `(display-mouse-p)' or no help text if
> `completion-show-help' is nil.

Good point, maybe minibuffer-completion-help is not the best place, but
it's closer than switch-to-completions.

> And there are many packages that
> don't call `minibuffer-completion-help' - they use something like
> (with-output-to-temp-buffer "*Completions*" (display-completion-list ...

Yes, this redundancy sucks, but it's another problem.

> Maybe `switch-to-completions' should simply call `(next-completion 1)'?
> It seems this is the most reliable way to move point to the first completion.

Fine by me.  Install your patch for now, but please include a comment
explaining that the cursor-movement should really be done elsewhere.


        Stefan