From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: sbaugh@janestreet.com, 70968@debbugs.gnu.org,
monnier@iro.umontreal.ca, juri@linkov.net
Subject: bug#70968: 29.2.50; choose-completion on an emacs22-style completion deletes text after point
Date: Sat, 14 Sep 2024 19:00:46 +0300 [thread overview]
Message-ID: <86bk0qfcnl.fsf@gnu.org> (raw)
In-Reply-To: <a20796c1-a431-4206-bb71-e3c005c55efc@gutov.dev> (message from Dmitry Gutov on Sat, 14 Sep 2024 18:18:46 +0300)
> Date: Sat, 14 Sep 2024 18:18:46 +0300
> Cc: monnier@iro.umontreal.ca, juri@linkov.net, 70968@debbugs.gnu.org
> From: Dmitry Gutov <dmitry@gutov.dev>
>
> > I'm okay with adding a new style, per B, but why do we need to
> > deprecate emacs22 at the same time? Let users who want this new
> > behavior customize their completion styles to use this new style
> > instead of emacs22.
>
> I don't envy the person who's going to write documentation and has to
> describe the distinction between these two styles, that they differ in
> this particular place of the UI, and are otherwise the same.
>
> Deprecating the old style would at least say that this complication is a
> wart which would someday go away, and we could take a shortcut in the
> implementation (e.g. hardcode the value `emacs22` in some check).
If documentation difficulties are the main issue with my proposal,
then you can stop worrying.
next prev parent reply other threads:[~2024-09-14 16:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 20:26 bug#70968: 29.2.50; choose-completion on an emacs22-style completion deletes text after point Spencer Baugh
2024-05-16 8:13 ` Eli Zaretskii
2024-05-16 17:26 ` Dmitry Gutov
2024-05-16 18:25 ` Eli Zaretskii
2024-08-26 0:08 ` Dmitry Gutov
2024-09-07 7:30 ` Eli Zaretskii
2024-09-08 2:02 ` Dmitry Gutov
2024-09-08 11:12 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-10 16:54 ` Spencer Baugh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-14 9:17 ` Eli Zaretskii
2024-09-14 15:18 ` Dmitry Gutov
2024-09-14 16:00 ` Eli Zaretskii [this message]
2024-09-16 19:54 ` Spencer Baugh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-24 0:03 ` Dmitry Gutov
2024-10-15 18:53 ` Spencer Baugh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-17 0:19 ` Dmitry Gutov
2024-10-22 0:10 ` Dmitry Gutov
2024-05-16 17:40 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-16 18:28 ` Eli Zaretskii
2024-06-20 15:45 ` Spencer Baugh
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=86bk0qfcnl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=70968@debbugs.gnu.org \
--cc=dmitry@gutov.dev \
--cc=juri@linkov.net \
--cc=monnier@iro.umontreal.ca \
--cc=sbaugh@janestreet.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.