From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: sbaugh@janestreet.com, juri@linkov.net, 70968@debbugs.gnu.org,
dmitry@gutov.dev
Subject: bug#70968: 29.2.50; choose-completion on an emacs22-style completion deletes text after point
Date: Thu, 16 May 2024 21:28:45 +0300 [thread overview]
Message-ID: <861q61ipb6.fsf@gnu.org> (raw)
In-Reply-To: <jwvcyplbr58.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Thu, 16 May 2024 13:40:35 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Spencer Baugh <sbaugh@janestreet.com>, dmitry@gutov.dev,
> 70968@debbugs.gnu.org, juri@linkov.net
> Date: Thu, 16 May 2024 13:40:35 -0400
>
> > If making these two ways consistent means we need to change the
> > behavior of emacs22 style of completion, then I'm sorry, but we cannot
> > do that. This style is a legacy style, and is there to provide the
> > legacy behavior for those who need it.
>
> I'm not sure it's terribly important to preserve this detail of the
> behavior of `Emacs-22`. The `emacs22` style does not aim to provide the
> illusion you're running an old Emacs. I named it that way because
> I couldn't come up with a good descriptive name for it. If it
> misbehaves, I don't see a need to be bug-compatible, especially since
> this doesn't affect ELisp code but users.
I think it does, sorry. Suchj old behavior is a de-facto standard.
If we change that, we should at least have a knob to get back the old
behavior.
next prev parent reply other threads:[~2024-05-16 18:28 UTC|newest]
Thread overview: 7+ 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-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 [this message]
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=861q61ipb6.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.