From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: larsi@gnus.org, stephen.berman@gmx.net, 36729@debbugs.gnu.org
Subject: bug#36729: 27.0.50; Unclear total in directory listing
Date: Wed, 07 Oct 2020 15:14:47 +0300 [thread overview]
Message-ID: <83zh4y8c7c.fsf@gnu.org> (raw)
In-Reply-To: <84AFB7F6-D925-4552-A165-927996C1C7B6@acm.org> (message from Mattias Engdegård on Wed, 7 Oct 2020 12:03:39 +0200)
> From: Mattias Engdegård <mattiase@acm.org>
> Date: Wed, 7 Oct 2020 12:03:39 +0200
> Cc: Lars Ingebrigtsen <larsi@gnus.org>, stephen.berman@gmx.net,
> 36729@debbugs.gnu.org
>
> 7 okt. 2020 kl. 09.50 skrev Eli Zaretskii <eliz@gnu.org>:
>
> > I no longer understand what we are trying to solve here.
>
> A bit lost here myself, but it seems that no real progress has been made and that the original problem (how to display a meaningful 'total' value in dired) is still at hand.
Yes.
> However given the apparent constraints (running an external 'ls' binary with unclear semantics; uncountable platform variations; user-settable 'ls' switches; sensitivity to environment variables; localised output; &c &c) I don't think it can be solved in any reasonable way. I therefore propose closing the bug as 'wontfix'.
You mean, we cannot even say in what units those numbers are measured?
AFAIU, the missing units were the original motivation for the bug
report.
next prev parent reply other threads:[~2020-10-07 12:14 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 [this message]
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
[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=83zh4y8c7c.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=36729@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mattiase@acm.org \
--cc=stephen.berman@gmx.net \
/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.