[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#65186: 29.0.91; `dired-free-space' is a step backward
From: |
Drew Adams |
Subject: |
bug#65186: 29.0.91; `dired-free-space' is a step backward |
Date: |
Thu, 10 Aug 2023 15:42:57 +0000 |
> > 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)