unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Sean Whitton <spwhitton@spwhitton.name>
To: Eshel Yaron <me@eshelyaron.com>
Cc: eliz@gnu.org, 73820@debbugs.gnu.org, jixiuf@qq.com,
	Juri Linkov <juri@linkov.net>
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 18:13:41 +0800	[thread overview]
Message-ID: <874j5c9wyy.fsf@melete.silentflame.com> (raw)
In-Reply-To: <m1h69c8pn4.fsf@macbookpro.home> (Eshel Yaron's message of "Wed,  16 Oct 2024 09:37:19 +0200")

Hello,

On Wed 16 Oct 2024 at 09:37am +02, Eshel Yaron wrote:

> 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.

If you were to look into that change, I would be very happy to review.

-- 
Sean Whitton





      parent reply	other threads:[~2024-10-16 10:13 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
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 [this message]

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=874j5c9wyy.fsf@melete.silentflame.com \
    --to=spwhitton@spwhitton.name \
    --cc=73820@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=jixiuf@qq.com \
    --cc=juri@linkov.net \
    --cc=me@eshelyaron.com \
    /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).