From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: 36729@debbugs.gnu.org
Subject: bug#36729: 27.0.50; Unclear total in directory listing
Date: Sat, 22 Aug 2020 16:00:08 +0200 [thread overview]
Message-ID: <875z9an5lj.fsf@gnus.org> (raw)
In-Reply-To: <048FD91B-CDA0-4444-8F6F-C5B2F5C595CD@acm.org> ("Mattias Engdegård"'s message of "Fri, 19 Jul 2019 12:15:58 +0200")
[-- Attachment #1: Type: text/plain, Size: 544 bytes --]
Mattias Engdegård <mattiase@acm.org> writes:
> The first line of a directory listing reads
>
> total used in directory 71752 available 65.2 GiB
>
> where it is a mystery what the first number represents. Often it is
> 512-byte blocks, which is confusing and not very useful, and cannot
> easily be compared with the 'available' number (which is crystal
> clear).
>
> It has always been thus, but previously the 'available' number was
> itself somewhat obscure so the first number didn't stand out.
Hm... My buffers read:
[-- Attachment #2: Type: image/png, Size: 14051 bytes --]
[-- Attachment #3: Type: text/plain, Size: 288 bytes --]
But that's because I have:
(setq dired-listing-switches "-alh")
It's confusing that it's doing the human-readable bit on the available
but not on the "used" with the default "-al".
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-08-22 14:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 10:15 bug#36729: 27.0.50; Unclear total in directory listing Mattias Engdegård
2019-07-19 12:16 ` Eli Zaretskii
2019-07-19 13:28 ` Stephen Berman
2019-07-19 15:18 ` Drew Adams
2020-08-22 14:02 ` Lars Ingebrigtsen
2020-08-26 10:10 ` Stephen Berman
2020-10-07 4:44 ` Lars Ingebrigtsen
2020-10-07 7:50 ` Eli Zaretskii
2020-10-07 10:03 ` Mattias Engdegård
2020-10-07 12:14 ` Eli Zaretskii
2020-10-07 13:50 ` Mattias Engdegård
2020-10-07 14:23 ` Eli Zaretskii
2020-10-07 14:52 ` Mattias Engdegård
2020-10-07 16:40 ` Michael Albinus
2020-10-08 7:45 ` Robert Pluim
2020-10-08 8:37 ` Michael Albinus
2019-07-21 8:19 ` Mattias Engdegård
2019-07-21 14:29 ` Eli Zaretskii
2019-07-21 18:36 ` Mattias Engdegård
2019-07-21 21:31 ` Drew Adams
2019-07-22 2:32 ` Eli Zaretskii
2019-07-22 2:30 ` Eli Zaretskii
2019-07-26 18:30 ` Juri Linkov
2020-08-22 14:00 ` Lars Ingebrigtsen [this message]
[not found] <<048FD91B-CDA0-4444-8F6F-C5B2F5C595CD@acm.org>
[not found] ` <<83k1ceusn1.fsf@gnu.org>
[not found] ` <<68D3B8E0-26F0-474A-B76D-320E523DBDDC@acm.org>
[not found] ` <<8336izsbok.fsf@gnu.org>
[not found] ` <<CFC507A0-42BE-40FF-AB46-3819B8714EB8@acm.org>
[not found] ` <<26fec456-c6bc-461f-8618-9cbc87cdde67@default>
[not found] ` <<83k1care8v.fsf@gnu.org>
2019-07-22 2:43 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875z9an5lj.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=36729@debbugs.gnu.org \
--cc=mattiase@acm.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.