From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "65186@debbugs.gnu.org" <65186@debbugs.gnu.org>
Subject: bug#65186: 29.0.91; `dired-free-space' is a step backward
Date: Thu, 10 Aug 2023 15:42:57 +0000 [thread overview]
Message-ID: <CO6PR10MB547330BC5BA8D2D1B24461C7F313A@CO6PR10MB5473.namprd10.prod.outlook.com> (raw)
In-Reply-To: <83sf8rjuhu.fsf@gnu.org>
> > Two main problems with this self-styled enhancement:
> >
> > 1. The default behavior should be what we've always had, which
> > corresponds to NONE of the `dired-free-space' option values.
>
> The 'separate' value (which is not the default) produces the behavior
> we had in Emacs 28 and older, so why do you say that "what we always
> had corresponds to none" of the option's values?
No, it doesn't. Not with `emacs -Q' on MS Windows (which uses ls-lisp), at least. Not in 28.2 or ANY earlier release, going back to when `dired-hide-details-mode' was first introduced. In all releases, if you use `(' to hide details then that "separate" line is one of the details that's _removed_.
> > 2. Even if you set the option to `separate', so you see the full info,
> > you can't get the superior previous behavior, which is that there's _no
> > such info_ shown when you hide details (`(').
> >
> > Instead, Someone(TM) maybe thought that those interested in what
> > Someone(TM) doesn't think interesting - the full info - always want to
> > see that info, even with details hidden. Blinders...
>
> I think it was just an oversight, now fixed on the emacs-29 branch.
Thank you very much, Eli.
(I don't build Emacs, but I'm guessing you mean what I hope you mean. ;-))
IF all you changed was to make `separate' be the default or IF it was only to hide all such info when hiding details, then that doesn't fix what I'd like to see fixed.
I'd like to see both:
1. The default behavior as it was before: when details aren't hidden, show the full info on a separate line, and when details are hidden, don't show any such info (available, used, etc.).
2. For _each_ of the option values: when details are hidden, don't show any such info. (Unless you add a separate option value for something different. At least let users get the old behavior exactly, as one possibility)
next prev parent reply other threads:[~2023-08-10 15:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 22:03 bug#65186: 29.0.91; `dired-free-space' is a step backward Drew Adams
2023-08-10 6:12 ` Eli Zaretskii
2023-08-10 15:42 ` Drew Adams [this message]
2023-08-10 17:43 ` Eli Zaretskii
2023-11-09 17:42 ` Drew Adams
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=CO6PR10MB547330BC5BA8D2D1B24461C7F313A@CO6PR10MB5473.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=65186@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).