From: Sean Whitton <spwhitton@spwhitton.name>
To: "João Távora" <joaotavora@gmail.com>
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: Thu, 23 Mar 2023 12:13:27 -0700 [thread overview]
Message-ID: <87h6ubffhk.fsf@melete.silentflame.com> (raw)
In-Reply-To: <87pm90vd7c.fsf@gmail.com> ("João Távora"'s message of "Wed, 22 Mar 2023 18:43:51 +0000")
Hello,
On Wed 22 Mar 2023 at 06:43PM GMT, João Távora wrote:
> Sean Whitton <spwhitton@spwhitton.name> writes:
>
>> Interesting idea. What do you think the advantages are? It's breaking
>> with how such things usually work, in Emacs and in other editors.
>
> I wouldn't call it breaking, it's just a different UI. Fido modes
> (fido-mode and fido-vertical-mode) work in the minibuffer which shares
> its display space with the echo area already, so I wouldn't think it's
> that odd.
Looking forward to trying it.
>> Since you're up for reviewing a patch to make icomplete-in-buffer work
>> with fido-mode, I assume you are interested in keeping both working?
>
> As I said, only if an elegant enough patch can be devised for the
> current icomplete-in-buffer functionality.
Cool.
--
Sean Whitton
prev parent reply other threads:[~2023-03-23 19:13 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
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 [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h6ubffhk.fsf@melete.silentflame.com \
--to=spwhitton@spwhitton.name \
--cc=61943@debbugs.gnu.org \
--cc=joaotavora@gmail.com \
--cc=juri@linkov.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.