GNU bug report logs -
#67661
30.0.50; *Completions* has started popping up for icomplete-in-buffer
Previous Next
Reported by: Sean Whitton <spwhitton <at> spwhitton.name>
Date: Wed, 6 Dec 2023 15:31:02 UTC
Severity: normal
Fixed in version 30.0.50
Done: Juri Linkov <juri <at> linkov.net>
Bug is archived. No further changes may be made.
Full log
Message #126 received at 67661 <at> debbugs.gnu.org (full text, mbox):
Hello,
On Sat 30 Dec 2023 at 07:50pm +02, Juri Linkov wrote:
>> | 4b. Insert text into *scratch*: (setopt icomplete-
>> | 5b. C-M-i
>> | - Emacsen 29 & 30: in-buffer Icomplete appears & *Completions* pops up.
>
> This is exactly how icomplete-in-buffer was intended to work.
Right, yeah, I now understand that.
In a previous message you said you think that icomplete-in-buffer is
unfinished, and you'd like to consider further changes to how it works.
Is that something you're still considering, or are you setting that
aside for the time being?
I ask because if you are happy with how things are now, we could close
this bug.
>> Secondly, the *Completions* buffer now always pops up at the same
>> time that Icomplete displays its in-buffer completion. If you would
>> prefer to see only Icomplete's display, which is what you might be
>> used to, you could use
>>
>> (advice-add 'completion-at-point :after #'minibuffer-hide-completions)
>>
>> The reason I haven't gone ahead and added this already is that Juri has
>> suggested further changing icomplete-in-buffer's default behaviour.
>> I don't think that we should do that.
>
> I suggested adding a new option that would disable popping up *Completions*.
> This is preferable to instructing users how to use advice-add. But this
> might be not quite straightforward to implement.
Yes, that would be preferable, if someone wants to work on it at some point.
--
Sean Whitton
This bug report was last modified 1 year and 184 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.