From: Juri Linkov <juri@linkov.net>
To: Carlos Pita <carlosjosepita@gmail.com>
Cc: 51575@debbugs.gnu.org
Subject: bug#51575: 28.0.60; Many issues with icomplete-in-buffer
Date: Mon, 27 Feb 2023 20:44:23 +0200 [thread overview]
Message-ID: <86a60zaqyg.fsf@mail.linkov.net> (raw)
In-Reply-To: <CAELgYhfpmjr0YHdx_TV3zHh+rg4fYiaBVLoegqcHGXNKHSaAiA@mail.gmail.com> (Carlos Pita's message of "Tue, 2 Nov 2021 19:41:06 -0300")
close 51575 30.0.50
thanks
> I would like to use fido-mode in completion in-region / at-point
> contexts. I realized there is a icomplete-in-buffer flag that is
> intended to do that, at least for icomplete. So I started emacs with:
>
> (setq icomplete-in-buffer t)
> (icomplete-mode 1)
>
> But the behavior is erratic to say the best. Say I'm in *scratch* and
> want to autocomplete some symbol:
>
> 1. Doing M-<tab> once shows the icomplete menu, doing it again replaces
> the *entire* buffer contents with just the selection.
>
> 2. Sometimes only the icomplete menu is shown, sometimes the traditional
> *Completions* buffer is shown at the same time.
>
> 3. Pressing Enter doesn't select the candidate but inserts Enter.
>
> 4. If I enable fido-mode it disables and re-enables icomplete-mode but
> leaves the icomplete completion-in-region-mode-hook uninstalled,
> disregarding icomplete-in-buffer.
>
> Maybe this is a legacy option that should be made obsolete, but it's a
> pity that vanilla emacs provides so many alternatives for
> completing-read but none for completion-at-point. The current
> implementation wants to show the menu at point, this probably makes it
> more complex, but simply showing the standard minibuffer icomplete
> interface at the bottom would be a lot (like for example selectrum
> does).
Thanks for the bug report. This is fixed now in Emacs 30
for icomplete-mode and fido-mode.
prev parent reply other threads:[~2023-02-27 18:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 22:41 bug#51575: 28.0.60; Many issues with icomplete-in-buffer Carlos Pita
2021-11-07 23:10 ` Carlos Pita
2023-02-27 18:44 ` Juri Linkov [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=86a60zaqyg.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=51575@debbugs.gnu.org \
--cc=carlosjosepita@gmail.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).