Subject: 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 15:26:32 +0200

> Date: Fri, 06 Jan 2023 13:10:18 +0000
> From: Gregory Heytings <[email-masked]>
> cc: [email-masked], [email-masked], [email-masked], 
>     [email-masked]
> 
> > Didn't you just say that the difference between "first" and "next" is 
> > "the first call"?  Can't we make the logic be based on that instead of 
> > assuming that the format produces an empty string under certain 
> > conditions?
> >
> 
> As far as I can see, no.  What is also possible, if it's the condition 
> that you don't like, is to insert that invisible line unconditionally, 
> like this:

If we cannot come up with any better ideas (which again surprises me),
then unconditionally adding such a newline is better.

But let's wait for Stefan to chime in.