From: Eli Zaretskii <eliz@gnu.org>
To: Eshel Yaron <me@eshelyaron.com>
Cc: emacs-devel@gnu.org
Subject: Re: Word completion in text modes
Date: Sat, 18 Nov 2023 21:18:44 +0200 [thread overview]
Message-ID: <834jhina3v.fsf@gnu.org> (raw)
In-Reply-To: <m15y1ysx2m.fsf@dazzs-mbp.home> (message from Eshel Yaron on Sat, 18 Nov 2023 20:03:45 +0100)
> From: Eshel Yaron <me@eshelyaron.com>
> Cc: emacs-devel@gnu.org
> Date: Sat, 18 Nov 2023 20:03:45 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > If we don't preserve that UI, we will be making an incompatible
> > change, which from my POV is undesirable. It doesn't matter whether
> > we like or dislike the ispell UI for this: compatibility means just
> > that. We could make the old UI an opt-in behavior, but tossing it
> > altogether is not something I'd welcome.
>
> I think we mostly agree then, because I didn't suggest tossing the old
> UI anywhere. To opt-in to the old behavior, you'd say:
>
> (keymap-set text-mode-map "C-M-i" #'ispell-complete-word)
>
> That seems to me like a simple enough tip for users that we could appear
> in a NEWS entry. Does that sound reasonable?
I'd prefer a solution that didn't require key bindings. Something
like a user option.
> >> Either way it'd be compatible in the sense that you get the same
> >> completions, and `ispell-complete-word` wouldn't go anywhere so
> >> users could rebind it if they really want to.
> >
> > That is not compatibility in my book, sorry. We should actually offer
> > a very similar or identical UI.
>
> Yes, I wonder just wonder how should we offer that UI. Doesn't keeping
> the command around for users to make use of cover it? Or do you mean
> there should be some user option for selecting the word completion UI?
I think an option will be better.
next prev parent reply other threads:[~2023-11-18 19:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-18 12:03 Word completion in text modes Eshel Yaron
2023-11-18 12:39 ` Eli Zaretskii
2023-11-18 13:21 ` Eshel Yaron
2023-11-18 13:50 ` Eli Zaretskii
2023-11-18 15:53 ` Eshel Yaron
2023-11-18 16:03 ` [External] : " Drew Adams
2023-11-18 16:37 ` Eli Zaretskii
2023-11-18 19:03 ` Eshel Yaron
2023-11-18 19:18 ` Eli Zaretskii [this message]
2023-11-21 13:45 ` Eshel Yaron
2023-11-25 10:40 ` Eli Zaretskii
2023-11-25 12:11 ` Eshel Yaron
2023-11-25 12:33 ` Eli Zaretskii
2023-11-25 13:00 ` Eshel Yaron
2023-11-26 10:31 ` Eli Zaretskii
2023-11-26 11:03 ` Eshel Yaron
2023-11-26 11:23 ` Eli Zaretskii
2023-11-18 16:05 ` [External] : " Drew Adams
2023-11-18 16:55 ` Juergen Fenn
2023-11-18 18:33 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834jhina3v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=me@eshelyaron.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 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.