unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 65186@debbugs.gnu.org
Subject: bug#65186: 29.0.91; `dired-free-space' is a step backward
Date: Thu, 10 Aug 2023 09:12:45 +0300	[thread overview]
Message-ID: <83sf8rjuhu.fsf@gnu.org> (raw)
In-Reply-To: <SJ0PR10MB54881F055A0737B4DF4B1722F312A@SJ0PR10MB5488.namprd10.prod.outlook.com> (message from Drew Adams on Wed, 9 Aug 2023 22:03:36 +0000)

> From: Drew Adams <drew.adams@oracle.com>
> Date: Wed, 9 Aug 2023 22:03:36 +0000
> 
> Dunno how such a change was made to the _default_ Emacs behavior.
> Shouldn't have happened, IMHO.
> 
> 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?

> 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.





  reply	other threads:[~2023-08-10  6:12 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 [this message]
2023-08-10 15:42   ` Drew Adams
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=83sf8rjuhu.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=65186@debbugs.gnu.org \
    --cc=drew.adams@oracle.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).