From: Paul Eggert <eggert@cs.ucla.edu>
To: Chandler Sobel-Sorenson <chandler@genome.arizona.edu>
Cc: 58521@debbugs.gnu.org
Subject: bug#58521: human readable still wrong output (after 20+ years?)
Date: Mon, 2 Jan 2023 13:40:22 -0800 [thread overview]
Message-ID: <c04e2bf0-f6ec-9221-6b60-fbb58855dc9a@cs.ucla.edu> (raw)
In-Reply-To: <5a0f115a-41de-4f75-05ff-5e486cd9c581@riseup.net>
On 2023-01-02 13:22, Chandler Sobel-Sorenson wrote:
>> Unfortunately backward-compatibility concerns are real,
>
> Such as?
I imagine lots of programs read the current output format. GNU 'sort'
does. I haven't investigated all such programs.
The current behavior has been in place since Larry McVoy contributed it
in 1996. It'd take a pretty strong argument to change it now. Mere
dislike wouldn't suffice.
> this is about your programs outputting WRONG and INCORRECT values,
> inconsistent with reality
"Inconsistent with reality" is hyperbole; this is merely disagreement
about notation.
> All you need to do is add an "i" to -h's prefixes
That would bloat the output and introduce compatibility concerns as
mentioned above.
prev parent reply other threads:[~2023-01-02 21:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 16:24 bug#58521: human readable still wrong output (after 20+ years?) chandler
2023-01-02 20:28 ` Paul Eggert
2023-01-02 21:22 ` Chandler Sobel-Sorenson
2023-01-02 21:40 ` Paul Eggert [this message]
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://lists.gnu.org/mailman/listinfo/bug-coreutils
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c04e2bf0-f6ec-9221-6b60-fbb58855dc9a@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=58521@debbugs.gnu.org \
--cc=chandler@genome.arizona.edu \
/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.
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).