From: Eli Zaretskii <eliz@gnu.org>
To: Leo Liu <sdl.web@gmail.com>
Cc: 63744@debbugs.gnu.org
Subject: bug#63744: 28.2; fix dired-guess-default
Date: Mon, 29 May 2023 15:38:21 +0300 [thread overview]
Message-ID: <83o7m3gvnm.fsf@gnu.org> (raw)
In-Reply-To: <m1fs7fiypk.fsf@gmail.com> (message from Leo Liu on Mon, 29 May 2023 11:49:27 +0800)
> From: Leo Liu <sdl.web@gmail.com>
> Date: Mon, 29 May 2023 11:49:27 +0800
>
> If we put all these details behind and look from the users' perspective,
> I wonder if there is a chance for Emacs 28.
It doesn't look like there will be another Emacs 28.x release.
And, given the change to the code, I don't think this is appropriate
for Emacs 29.1, either. It's too late for such changes on the release
branch.
> Basically this feature has been there and working since at least Emacs
> 24 (or even earlier). It may be an accident which I only discovered last
> week though the bug has been annoying me for a few months since I
> upgraded from Emacs 27. For users this is a regression and it's bad.
If it's a bad regression, why didn't we hear about it until now?
Emacs 28.1 was released more than a year ago, and was in pretest for
several months before that. My guess would be that this accidental
"feature" is not used frequently enough to be a bad regression.
And I don't object to extending Dired in this way, I just don't think
we should do that in Emacs 29. There are enough real bad problems and
regressions that block its release, and I'm not thrilled adding
another non-trivial change so late. Sorry.
next prev parent reply other threads:[~2023-05-29 12:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-27 4:10 bug#63744: 28.2; fix dired-guess-default Leo Liu
2023-05-27 6:49 ` Eli Zaretskii
2023-05-28 2:40 ` Leo Liu
2023-05-28 6:27 ` Eli Zaretskii
2023-05-29 1:23 ` Michael Heerdegen
2023-05-29 3:49 ` Leo Liu
2023-05-29 12:38 ` Eli Zaretskii [this message]
2023-05-30 0:04 ` Michael Heerdegen
2023-05-29 12:07 ` Eli Zaretskii
2023-05-29 18:20 ` Leo Liu
2023-05-29 18:27 ` Eli Zaretskii
2023-05-30 0:24 ` Michael Heerdegen
2023-05-30 2:36 ` Eli Zaretskii
2023-06-02 0:14 ` Michael Heerdegen
2023-06-02 4:28 ` Leo Liu
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=83o7m3gvnm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=63744@debbugs.gnu.org \
--cc=sdl.web@gmail.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).