unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Sean Whitton <spwhitton@spwhitton.name>, Eli Zaretskii <eliz@gnu.org>
Cc: 61943@debbugs.gnu.org, juri@linkov.net
Subject: bug#61943: 29.0.60; icomplete--in-region-setup should activate icomplete-fido-mode-map too
Date: Sat, 4 Mar 2023 11:30:48 +0000	[thread overview]
Message-ID: <CALDnm52DGtgvf+ft6RLJ9NOodKo=NZLPzQMqGvn99+eCf+PwEg@mail.gmail.com> (raw)
In-Reply-To: <87h6v1s0p4.fsf@melete.silentflame.com>

On Sat, Mar 4, 2023 at 2:35 AM Sean Whitton <spwhitton@spwhitton.name> wrote:
>
> Hello,
>
> On Fri 03 Mar 2023 at 11:18AM -07, Sean Whitton wrote:
>
> > X-debbugs-cc: juri@linkov.net, joaotavora@gmail.com
> >
> > Many thanks to Juri and Joao for fixing #45763!  It's a whole new world!
> >
> > I am a fido-mode user.  I noticed that my custom bindings for the
> > fido-mode minibuffer don't work for in-buffer completion.  I think that
> > icomplete--in-region-setup should compose in icomplete-fido-mode-map, in
> > addition to icomplete-minibuffer-map, in the case that fido-mode is on?
>
> I noticed that icomplete-hide-common-prefix etc. are wrong too.
> I think that icomplete--in-region-setup also needs to do something
> equivalent to the setq-local in icomplete--fido-mode-setup.

Yes, Sean, please report an Emacs -Q recipe for what you are trying
to get working.

I've now found a way to test this, and I was surprised at how easy it
was, but also skeptical.  As I remember analyzing it more than a year ago,
and finding this a reasonbaly hard job.  Also it seems to be completely
broken for fido-vertical mode and icomplete-vertical-mode, so I think
an approach that takes these cousin modes into consideration.

All in all, I'm not sure we should be shipping this half-baked
enhancement for emacs-29, at least not in this phase. I propose
we revert it in emacs-29.

I propose we revert it from there, keep the changes in master,
and focus on making it more consistent there.





  reply	other threads:[~2023-03-04 11:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-03 18:18 bug#61943: 29.0.60; icomplete--in-region-setup should activate icomplete-fido-mode-map too Sean Whitton
2023-03-03 20:26 ` João Távora
2023-03-04  2:13   ` Sean Whitton
2023-03-04  2:35 ` Sean Whitton
2023-03-04 11:30   ` João Távora [this message]
2023-03-04 18:52     ` Juri Linkov
2023-03-04 19:04       ` João Távora
2023-03-04 19:14         ` Juri Linkov
2023-03-04 20:44     ` Sean Whitton
2023-03-21 22:06       ` Sean Whitton
2023-03-21 23:40         ` João Távora
2023-03-22 17:25           ` Sean Whitton
2023-03-22 18:43             ` João Távora
2023-03-23 19: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

  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='CALDnm52DGtgvf+ft6RLJ9NOodKo=NZLPzQMqGvn99+eCf+PwEg@mail.gmail.com' \
    --to=joaotavora@gmail.com \
    --cc=61943@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=juri@linkov.net \
    --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 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).