[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: |
Juri Linkov |
Subject: |
bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer |
Date: |
Tue, 19 Dec 2023 20:58:04 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/30.0.50 (x86_64-pc-linux-gnu) |
>> 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`.
>
> When I said "provide both", I meant both your idea of how the feature
> should work, and my idea of how it should work. I didn't mean both the
> in-buffer candidates and the *Completions* buffer.
>
> What you've said isn't true, though: a single TAB, which is bound to
> completion-at-point in Eshell, does not show in-buffer candidates, nor
> does it pop up the *Completions* buffer.
Because ls<TAB> is complete, but not unique. So it requires the second TAB,
exactly as in the minibuffer. A single TAB does this on incomplete candidate,
e.g. l<TAB>.
- 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, Eshel Yaron, 2023/12/09
- bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer, Sean Whitton, 2023/12/09
- bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer, Juri Linkov, 2023/12/09
- bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer, Sean Whitton, 2023/12/09
- bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer, Juri Linkov, 2023/12/10
- bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer, Sean Whitton, 2023/12/10
- bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer, Juri Linkov, 2023/12/11
- 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 <=
- 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, 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, 2023/12/30
- bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer, Sean Whitton, 2023/12/30