[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#67661: 30.0.50; *Completions* has started popping up for icomplete-i
From: |
Eli Zaretskii |
Subject: |
bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer |
Date: |
Fri, 29 Dec 2023 21:27:00 +0200 |
> From: Sean Whitton <spwhitton@spwhitton.name>
> Cc: 67661@debbugs.gnu.org
> Date: Fri, 29 Dec 2023 18:00:29 +0000
>
> Hello,
>
> On Fri 29 Dec 2023 at 05:47pm GMT, Sean Whitton wrote:
>
> > I'm not sure whether to close the bug or not, because there remains the
> > behavioural change for icomplete-in-buffer since Emacs 29.1.
>
> I've found a work around for the behavioural change:
>
> (setopt completion-auto-help t)
> (advice-add 'completion-at-point :after #'minibuffer-hide-completions)
>
> So maybe we should just add something explaining this to NEWS?
To which entry in Emacs 29's NEWS would this be related?
> The default value of completion-auto-help is t, but I had it set to
> `lazy'.
> If someone wants the Emacs 29 behaviour back, they'll need to ensure
> completion-auto-help is t, so I think we should mention it somewhere.
> Essentially, completion-auto-help now affects both the *Completions*
> buffer and icomplete-in-buffer's display.
If your change modifies the default behavior, that should be called
out in NEWS of Emacs 30.
- bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer, (continued)
- bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer, Sean Whitton, 2023/12/15
- bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer, Juri Linkov, 2023/12/19
- bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer, Sean Whitton, 2023/12/19
- bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer, Juri Linkov, 2023/12/19
- bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer, Sean Whitton, 2023/12/20
- bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer, Juri Linkov, 2023/12/20
- bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer, Sean Whitton, 2023/12/22
- bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer, Juri Linkov, 2023/12/23
- bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer, Sean Whitton, 2023/12/29
- bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer, Sean Whitton, 2023/12/29
- bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer,
Eli Zaretskii <=
- bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer, Sean Whitton, 2023/12/29
- bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer, Eli Zaretskii, 2023/12/30
- bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer, Sean Whitton, 2023/12/30
- bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer, Juri Linkov, 2023/12/30
- bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer, Sean Whitton, 2023/12/30
- bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer, Juri Linkov, 2023/12/30
- bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer, Sean Whitton, 2023/12/30
- bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer, Juri Linkov, 2023/12/31
- bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer, Eli Zaretskii, 2023/12/09
bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer, Juri Linkov, 2023/12/07