From: Eli Zaretskii <eliz@gnu.org>
To: Eshel Yaron <me@eshelyaron.com>
Cc: juri@linkov.net, 73820@debbugs.gnu.org, jixiuf@qq.com,
spwhitton@spwhitton.name
Subject: bug#73820: 31.0.50; [Feature Request]how to hide *Completions* buffer when icomplete-in-buffer is not nil
Date: Wed, 16 Oct 2024 12:07:27 +0300 [thread overview]
Message-ID: <8634kwquuo.fsf@gnu.org> (raw)
In-Reply-To: <m1h69c8pn4.fsf@macbookpro.home> (message from Eshel Yaron on Wed, 16 Oct 2024 09:37:19 +0200)
> From: Eshel Yaron <me@eshelyaron.com>
> Cc: eliz@gnu.org, jixiuf@qq.com, Sean Whitton <spwhitton@spwhitton.name>,
> Juri Linkov <juri@linkov.net>
> Date: Wed, 16 Oct 2024 09:37:19 +0200
>
> >> Right. This is also stated in NEWS.
> >
> > If this is important enough, it should be in the doc string. So I've
> > now added this tip to the doc string, and I'm therefore closing this
> > bug.
>
> Hmm, I'm not sure that that's really such a good recommendation. Adding
> this advice breaks M-: completion, for example. I think a more refined
> solution is due, if this is to be considered a supported use case...
> Namely, I suggest implementing icomplete-in-buffer as a
> completion-in-region-function, like some other in-buffer completion
> frontends are implemented.
Of course, a better solution, especially if it is not based on
advising functions, are always welcome. But I'm guessing the solution
you have in mind is not for the release branch, though?
next prev parent reply other threads:[~2024-10-16 9:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 11:01 bug#73820: 31.0.50; [Feature Request]how to hide *Completions* buffer when icomplete-in-buffer is not nil jixiuf@qq.com via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-15 16:43 ` Juri Linkov
2024-10-16 1:23 ` Sean Whitton
2024-10-16 5:33 ` Eli Zaretskii
2024-10-16 7:37 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-16 9:07 ` Eli Zaretskii [this message]
2024-10-16 9:36 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-16 10:13 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8634kwquuo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=73820@debbugs.gnu.org \
--cc=jixiuf@qq.com \
--cc=juri@linkov.net \
--cc=me@eshelyaron.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.