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
View this message in rfc822 format
>>>> (completion--in-region-1 start end)
>>>>
>>>> If you just remove this line from `completion--in-region` then
>>>> it should work like you expected without popping up *Completions*.
>>>
>>> Thanks, that does indeed restore the behaviour.
>>>
>>> Should we change this to a different completion-in-region-function in
>>> icomplete.el, then? Or what did you have in mind?
>>
>> What I think is that ideally icomplete-in-buffer in a regular buffer
>> should work like in the minibuffer, i.e. to be active all the time.
>> This is more like completion-preview-mode where in-buffer candidates
>> are shown as you type, whereas explicitly typing M-C-i pops up
>> the *Completions* buffer. Do you agree this would be nice to do?
>
> Hmm. This is an interesting idea. I don't think it would suit me,
> though -- it sounds like it would be quite visually noisy. Do you think
> we can provide both?
Both are already shown: M-C-i pops up the *Completions* buffer
and activates in-buffer candidates. If you want M-C-i only
to activate in-buffer candidates, then the line above
should be removed from `completion--in-region`.
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.