From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: sbaugh@janestreet.com, juri@linkov.net, 70968@debbugs.gnu.org,
Dmitry Gutov <dmitry@gutov.dev>
Subject: bug#70968: 29.2.50; choose-completion on an emacs22-style completion deletes text after point
Date: Sun, 08 Sep 2024 07:12:47 -0400 [thread overview]
Message-ID: <jwvjzfmcsfv.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <86ed5vzzru.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 07 Sep 2024 10:30:45 +0300")
> Ping! How should we proceed with this bug report?
I don't quite understand the question.
After:
Eli wrote:
> Stefan wrote:
> > 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.
I thought you had decided that the current behavior is not a bug.
I'm fine with this choice and we can close it as such.
Tho maybe we'd want to deprecate that `emacs22` style because of
those odd cases.
Stefan
next prev parent reply other threads:[~2024-09-08 11:12 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 [this message]
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
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
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=jwvjzfmcsfv.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=70968@debbugs.gnu.org \
--cc=dmitry@gutov.dev \
--cc=eliz@gnu.org \
--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 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).