bug#81631: 32.0.50; setting completion-auto-select t when completions-format is 'vertical doesn't returns to the minibuffer when cycling

Lucas Jimenez via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <[email protected]>
Newsgroups gmane.emacs.bugs
Message-ID <[email protected]>
I didn’t know you were describing your issue (1) with the applied patched.  Now I do.
After your patch is applied I see the same behavior with ‘vertical and ‘horizontal.


> I don't quite understand what you're describing.  Can you give a step by
> step reproducer with specific input starting emacs with -Q?

What I mean, after applying your patch, is this:


The step by step is this:

1) Start emacs with:
emacs -Q --eval "(setq completions-format 'horizontal completion-auto-select t)”

2) The try complete in here and I notice it does the full cycle the same with ‘horizontal (Ending in slash):
C-x C-f ~/.emacs.d/

3) BUT if I try to complete like this it gets stuck like you mentioned in issue (1) (notice the ‘e’ in the completion for a file):
C-x C-f ~/.emacs.d/e


In conclusion: If I try completion in a directory (ending with /) it does the full cycle, and if I try to complete a file it gets stuck.  So I don’t know if the problem is the annotation, since when trying to complete a file there is no annotation and it gets stuck.  Hope this is more clear

Thanks

> On 17-08-2026, at 05:47, Stephen Berman <[email protected]> wrote:
> 
> On Sun, 16 Aug 2026 20:02:07 -0400 Lucas Jimenez <[email protected]> wrote:
> 
>> This one it cycled to the minibuffer after last candidate, but then it got
>> stucked cycling between the minibuffer and the last candidate not returning to
>> the first cycle to cycle all over again.
> 
> This sounds like issue (1) mentioned below.  If so, you'll see the same
> behavior when completions-format is 'horizontal.  I reported this in
> bug#81635 and posted a fix; if you apply that fix as well as the patch I
> posted to make cycling through the minibuffer work in vertical format,
> then you should get the desired cycling behavior in both horizontal and
> vertical formats (unless you hit issue (2), e.g. with `M-x dabbrev- TAB').
> 
>>                                          On another instance it cycled, but
>> it went like this: last_candidate->minibuffer->closes the minibuffer->opens
>> the minibuffer to select first candidate and cycle again.  The difference is
>> that in the first I had typed a character to complete and in the later it
>> didn’t have anything typed to complete.
> 
> I don't quite understand what you're describing.  Can you give a step by
> step reproducer with specific input starting emacs with -Q?
> 
> Steve Berman
> 
> 
>>> On 16-08-2026, at 12:05, Stephen Berman <[email protected]> wrote:
>>> 
>>> On Sat, 15 Aug 2026 09:10:23 -0400 Lucas Jimenez via "Bug reports for GNU
>> Emacs, the Swiss army knife of text editors" <[email protected]
>> <mailto:[email protected]>> wrote:
>>> 
>>>> Hi,
>>>> 
>>>> Setting completions-format 'vertical and completion-auto-select t
>>>> doesn't cycle to the minibuffer when tapping TAB.
>>>> 
>>>> This behavior is expected since it is the one 'one-column uses and also
>>>> 'horizontal
>>>> 
>>>> Reproduce with:
>>>> 
>>>> emacs -Q --eval "(setq completions-format 'vertical
>>>> completion-auto-select t)"
>>> 
>>> Thanks for this report; I overlooked this behavior of TAB when I made
>>> the changes in 77ca60b48d01.  The attached patch adds this behavior to
>>> the vertical format; can you confirm?
>>> 
>>> However, while testing I noticed two issues: (1) on entering the
>>> minibuffer from the *Completions* buffer, typing TAB returns to the last
>>> completion candidate rather then going the the first, thus breaking the
>>> cycling behavior (likewise for S-TAB); I will file a separate bug report
>>> about this and propose a fix.  (2) Navigation through the *Completions*
>>> buffer has problems when the completions are annotated (e.g. with key
>>> bindings); I haven't debugged this yet but when I do I'll file a
>>> separate bug.
>>> 
>>> Steve Berman
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.