unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: rms@gnu.org, juri@linkov.net, stefankangas@gmail.com,
	larsi@gnus.org, jidanni@jidanni.org, 44273@debbugs.gnu.org
Subject: bug#44273: "total used in directory 19 available 5.2 GiB"
Date: Sun, 01 Nov 2020 17:21:21 +0200	[thread overview]
Message-ID: <83tuu9f6ha.fsf@gnu.org> (raw)
In-Reply-To: <329AE9D0-14BB-477E-AA7F-FC5852F67A7E@acm.org> (message from Mattias Engdegård on Sun, 1 Nov 2020 12:55:23 +0100)

> From: Mattias Engdegård <mattiase@acm.org>
> Date: Sun, 1 Nov 2020 12:55:23 +0100
> Cc: Juri Linkov <juri@linkov.net>, Eli Zaretskii <eliz@gnu.org>, rms@gnu.org,
>         jidanni@jidanni.org, stefankangas@gmail.com, 44273@debbugs.gnu.org
> 
> 1 nov. 2020 kl. 12.38 skrev Lars Ingebrigtsen <larsi@gnus.org>:
> 
> > It only displays the space used directly in the current directory, which
> > is (in general) not interesting information.  (I.e., it doesn't descend
> > into sub-directories and count the usage there, so in any directory that
> > has a sub-directory, the data is misleading at best.)
> 
> Right, and it's worse. Even if we knew exactly the unit used (sectors, kibibytes, imperial qubits), what we get for a subdirectory is still platform-dependent.
> 
> Except that it's worse than that. The semantics may vary between file-systems on a single machine.
> 
> Except that it's even worse. It may depend on the history of the subdirectory. For instance, it could be the maximum number of disk hardware sectors used for the internal representation of some of the metadata for that directory at any time in the past. (This is probably the original meaning of the number.)

This actually means that this value provides information that is not
directly available in the file sizes.  So it is useful.

I find the notion that we should remove from display a useful quantity
just because it might be tricky to interpret in some situation,
especially by people who are not proficient in this stuff.  'ls' shows
it, and Dired isn't supposed to lose stuff that 'ls -al' provides.





  reply	other threads:[~2020-11-01 15:21 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-28  5:12 bug#44273: "total used in directory 19 available 5.2 GiB" 積丹尼 Dan Jacobson
2020-10-28 10:37 ` Mattias Engdegård
2020-10-28 10:43   ` Lars Ingebrigtsen
2020-10-28 10:53     ` Mattias Engdegård
2020-10-28 11:02       ` Lars Ingebrigtsen
2020-10-28 11:18         ` Mattias Engdegård
2020-10-28 11:23           ` Lars Ingebrigtsen
2020-10-28 11:47             ` Andreas Schwab
2020-10-28 12:10               ` Lars Ingebrigtsen
2020-10-28 12:18                 ` Mattias Engdegård
2020-10-28 12:26                   ` Andreas Schwab
2020-10-28 12:29                   ` Lars Ingebrigtsen
2020-10-28 15:38               ` Eli Zaretskii
2020-10-28 15:34             ` Eli Zaretskii
2020-10-29  8:36               ` Michael Albinus
2020-10-28 14:39           ` Drew Adams
2020-10-28 14:49             ` Mattias Engdegård
2020-10-28 15:28         ` Eli Zaretskii
2020-10-30 11:36           ` Lars Ingebrigtsen
2020-10-30 11:41             ` Eli Zaretskii
2020-10-31  9:44           ` Eli Zaretskii
2020-10-28 15:19     ` Eli Zaretskii
2020-10-28 15:55       ` Stefan Kangas
2020-10-28 15:59         ` Eli Zaretskii
2020-10-29  0:03           ` Stefan Kangas
2020-10-29  3:34             ` Eli Zaretskii
2020-10-29  8:48               ` Andreas Schwab
2020-10-30  3:05               ` Richard Stallman
2020-10-30  7:18                 ` Juri Linkov
2020-10-30  8:17                   ` Eli Zaretskii
2020-10-30 11:33                     ` Lars Ingebrigtsen
2020-10-30 11:39                       ` Eli Zaretskii
2020-10-30 11:41                         ` Lars Ingebrigtsen
2020-10-30 11:49                           ` Eli Zaretskii
2020-11-01 11:33                             ` Lars Ingebrigtsen
2020-10-31 19:14                           ` Juri Linkov
2020-11-01 11:38                             ` Lars Ingebrigtsen
2020-11-01 11:55                               ` Mattias Engdegård
2020-11-01 15:21                                 ` Eli Zaretskii [this message]
2020-11-01 15:41                                   ` Mattias Engdegård
2020-11-01 15:51                                     ` Eli Zaretskii
2020-11-01 16:37                                       ` Mattias Engdegård
2020-11-01 19:25                                         ` Jean Louis
2021-10-11 12:35                                         ` Stefan Kangas
2020-11-01 19:16                                     ` Jean Louis
2020-11-01 18:57                                   ` Jean Louis
2020-11-01 19:33                                     ` Eli Zaretskii
2020-11-01 19:38                               ` 積丹尼 Dan Jacobson
2020-11-01 19:43                                 ` Eli Zaretskii
2020-11-01 19:51                                   ` 積丹尼 Dan Jacobson
2020-10-31  4:47                     ` Richard Stallman
2020-10-30 19:03                   ` Drew Adams
2020-11-03  3:17                     ` Drew Adams
2020-11-03 18:39                       ` Juri Linkov
2020-11-03 19:51                         ` Drew Adams
2020-11-04 19:41                           ` Juri Linkov
2020-11-04 20:53                             ` Drew Adams
2020-10-30 11:34       ` Lars Ingebrigtsen
2020-10-29  4:54 ` Richard Stallman
2020-10-30 12:22   ` Lars Ingebrigtsen
2020-10-30 12:25     ` Eli Zaretskii
2020-10-30 13:39       ` Michael Albinus
2020-10-30 13:46         ` Eli Zaretskii
2020-10-30 14:54           ` Michael Albinus
2020-10-31  0:12           ` 積丹尼 Dan Jacobson
2020-10-31  4:45             ` Richard Stallman
2020-10-31  4:47         ` Richard Stallman
2020-10-31  4:47     ` Richard Stallman

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=83tuu9f6ha.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=44273@debbugs.gnu.org \
    --cc=jidanni@jidanni.org \
    --cc=juri@linkov.net \
    --cc=larsi@gnus.org \
    --cc=mattiase@acm.org \
    --cc=rms@gnu.org \
    --cc=stefankangas@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).