unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 45768@debbugs.gnu.org, simon254@mailbox.org,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	45767@debbugs.gnu.org
Subject: bug#45767: bug#45768: icomplete-mode does not provide in region completion for dabbrev-completion
Date: Mon, 09 May 2022 21:41:13 +0300	[thread overview]
Message-ID: <8635hi1rcm.fsf@mail.linkov.net> (raw)
In-Reply-To: <871qx3ca18.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 09 May 2022 11:47:31 +0200")

>> Could you explain where do you see that icomplete-mode is not invoked?
>> Should it enable icomplete keys in the buffer?  Or there is some
>> visual difference before the fixes and after?
>
> Stefan fixed this now, I think?

How do you see that it's fixed?





  reply	other threads:[~2022-05-09 18:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-10 12:37 bug#45767: icomplete-in-buffer completion does not work with dabbrev-completion simon254--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-06 19:04 ` bug#45767: bug#45768: icomplete-mode does not provide in region completion for dabbrev-completion Lars Ingebrigtsen
2022-05-06 19:38   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-07 10:16     ` Lars Ingebrigtsen
2022-05-07 14:22       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-07 15:51         ` Lars Ingebrigtsen
2022-05-08 18:08   ` bug#45768: " Juri Linkov
2022-05-09  9:47     ` Lars Ingebrigtsen
2022-05-09 18:41       ` Juri Linkov [this message]
2022-05-09 21:23         ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-19 16:58           ` Juri Linkov

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=8635hi1rcm.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=45767@debbugs.gnu.org \
    --cc=45768@debbugs.gnu.org \
    --cc=larsi@gnus.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).