Re: Suggestions for improvements to the *Completions* buffer

[Philip Kaludercic]

Philip Kaludercic <philipk@posteo.net> writes:

> Juri Linkov <juri@linkov.net> writes:
>
>>> +(defcustom completion-wrap-movement t
>>> +  "Non-nil means to wrap around when selecting completion options.
>>> +This affects the commands `next-completion' and
>>> +`previous-completion'."
>>> +  :type 'boolean
>>> +  :version "29.1"
>>> +  :group 'completion)
>>
>> It seems now completion-wrap-movement has no effect:
>> typing n, p, <right> or <left> eventually switches to the minibuffer,
>> where continuing typing these keys uses other commands.
>
> True, the only way I see right now to avoid this would be to check if
> tab/backtab was used before switching to the minibuffer, and otherwise
> wrap within the completions buffer.

I have tried this behaviour out, and it seems reasonable.

0002-Allow-for-next-completion-to-wrap-around-the-complet.patch
Description: Text Data

-- 
        Philip Kaludercic