From: Eli Zaretskii <eliz@gnu.org>
To: Sean Whitton <spwhitton@spwhitton.name>
Cc: 67661@debbugs.gnu.org, juri@linkov.net
Subject: bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer
Date: Fri, 08 Dec 2023 08:28:48 +0200 [thread overview]
Message-ID: <83lea51a3j.fsf@gnu.org> (raw)
In-Reply-To: <87msul4ql9.fsf@zephyr.silentflame.com> (message from Sean Whitton on Thu, 07 Dec 2023 22:04:18 +0000)
> Cc: 67661@debbugs.gnu.org
> From: Sean Whitton <spwhitton@spwhitton.name>
> Date: Thu, 07 Dec 2023 22:04:18 +0000
>
> Hello,
>
> On Thu 07 Dec 2023 at 07:28pm +02, Juri Linkov wrote:
>
> >> 1. emacs -q
> >> 2. (setopt icomplete-in-buffer t)
> >> 3. M-x icomplete-mode
> >> 4. M-x eshell
> >> 5. try to tab-complete something where there is more than one possible
> >> completion, e.g. ls<TAB> in a directory with many files.
> >>
> >> Previously you would get the icomplete in buffer completion.
> >> Now, additionally, *Completions* pops up, but it doesn't make sense to
> >> have both.
> >
> > It's possible to hide *Completions* when icomplete-mode is enabled,
> > but I'm not sure if everyone will like this. For example,
> > I'm using both icomplete-mode and the *Completions* buffer
> > at the same time in the minibuffer. And in a regular buffer
> > we should keep for users the ability to pop up *Completions*
> > in addition to in-buffer completions.
> >
> > Maybe the best solution would be to use something like
> > in completion-preview-mode where you can use in-buffer
> > completions and still be able to type M-C-i to pop up
> > the *Completions* buffer.
>
> This is a regression though, right? It didn't use to pop up.
Once again: it did. The *Completions* buffer always popped up the
second time you type TAB. The problem here is that the first TAB
doesn't show the in-buffer completion. _That_ is the regression we
should try fixing.
next prev parent reply other threads:[~2023-12-08 6:28 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 15:30 bug#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer Sean Whitton
2023-12-06 17:13 ` Juri Linkov
2023-12-06 18:14 ` Sean Whitton
2023-12-06 18:41 ` Eli Zaretskii
2023-12-07 11:42 ` Sean Whitton
2023-12-09 12:09 ` Sean Whitton
2023-12-09 13:08 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-09 13:25 ` Eli Zaretskii
2023-12-09 14:13 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-09 14:40 ` Eli Zaretskii
2023-12-09 15:22 ` Sean Whitton
2023-12-09 16:03 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-09 16:07 ` Sean Whitton
2023-12-09 17:19 ` Juri Linkov
2023-12-09 19:04 ` Sean Whitton
2023-12-10 17:46 ` Juri Linkov
2023-12-10 21:42 ` Sean Whitton
2023-12-11 17:15 ` Juri Linkov
2023-12-15 12:28 ` Sean Whitton
2023-12-19 17:29 ` Juri Linkov
2023-12-19 18:31 ` Sean Whitton
2023-12-19 18:58 ` Juri Linkov
2023-12-20 10:34 ` Sean Whitton
2023-12-20 17:14 ` Juri Linkov
2023-12-22 12:00 ` Sean Whitton
2023-12-23 17:38 ` Juri Linkov
2023-12-29 17:47 ` Sean Whitton
2023-12-29 18:00 ` Sean Whitton
2023-12-29 19:27 ` Eli Zaretskii
2023-12-29 20:24 ` Sean Whitton
2023-12-30 6:30 ` Eli Zaretskii
2023-12-30 10:41 ` Sean Whitton
2023-12-30 17:52 ` Juri Linkov
2023-12-30 19:43 ` Sean Whitton
2023-12-30 17:50 ` Juri Linkov
2023-12-30 19:43 ` Sean Whitton
2023-12-31 8:29 ` Juri Linkov
2024-01-10 3:12 ` john muhl via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-10 17:55 ` Sean Whitton
2024-01-17 19:18 ` Jim Porter
2023-12-09 16:22 ` Eli Zaretskii
2023-12-07 17:28 ` Juri Linkov
2023-12-07 22:04 ` Sean Whitton
2023-12-08 6:28 ` Eli Zaretskii [this message]
2023-12-08 10:19 ` Sean Whitton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83lea51a3j.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=67661@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=spwhitton@spwhitton.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).