From: Lars Ingebrigtsen <larsi@gnus.org>
To: simon254@mailbox.org
Cc: 45764@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#45764: icomplete in buffer completion does not work for completion-at-point
Date: Tue, 07 Jun 2022 15:25:29 +0200 [thread overview]
Message-ID: <87y1y8hagm.fsf@gnus.org> (raw)
In-Reply-To: <140804236.117906.1610282126510@office.mailbox.org> (simon's message of "Sun, 10 Jan 2021 12:35:26 +0000 (GMT)")
simon254@mailbox.org writes:
> emacs -Q
> in *scratch* eval
> (setq icomplete-in-buffer t)
> (icomplete-mode t)
> type:
> "(icompl" followed by C-M-i (completion-at-point) select icomplete-mode via C-j
> -> *scratch* buffer is now empty apart from icomplete-mode ; all other text is deleted
>
> it works however in shell mode for directory completion (tab invokes icomplete-mode)
(I'm going through old bug reports that unfortunately weren't resolved
at the time.)
`C-j' is bound to `icomplete-force-complete-and-exit', and it calls
`minibuffer-force-complete-and-exit' unconditionally, which deletes the
buffer contents. I can't get icomplete-in-buffer to work in either
*shell* or in other modes -- has this feature gotten much testing/use?
Are there cases where it works?
Adding Stefan to the CCs, since he hadded this in 2013.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-06-07 13:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-10 12:35 bug#45764: icomplete in buffer completion does not work for completion-at-point simon254--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-07 13:25 ` Lars Ingebrigtsen [this message]
2022-06-07 14:43 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-08 11:50 ` Lars Ingebrigtsen
2023-02-27 18:33 ` Juri Linkov
2023-02-27 18:57 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87y1y8hagm.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=45764@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=simon254@mailbox.org \
/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).