Subject: Re: bug#60411: 29.0.60; minibuffer-next-completion skips first candidate when completions-header-format and completion-show-help are nil

From: Eli Zaretskii <[email-masked]>
Date: Fri, 06 Jan 2023 20:11:10 +0200

> From: Stefan Monnier <[email-masked]>
> Cc: Gregory Heytings <[email-masked]>,  [email-masked],
>   [email-masked],  [email-masked]
> Date: Fri, 06 Jan 2023 12:51:41 -0500
> 
> >> > Then why not change that logic in minibuffer-next-completion to be 
> >> > smarter about this?
> >> I (and Stefan) already tried this, it doesn't seem to be feasible with a 
> >> small and safe change.
> > That's very surprising to hear.  AFAIU, it just looks for some special
> > text property (in next-completion).  So it sounds like a very simple
> > breakage of logic, where "next" means "the first one" when you are
> > exactly at BOB.
> 
> The problem is how to determine "this is the first time".  Currently we
> encode that information indirectly by the fact that point as at BOB
> (and is not on an actual completion).

Gregory just suggested a patch which does that in a fairly simple and
straightforward way.