From: Greg 'groggy' Lehey <grog@lemis.com>
To: Doug McIlroy <doug@cs.dartmouth.edu>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Command options and complexity
Date: Fri, 13 Mar 2020 15:25:27 +1100 [thread overview]
Message-ID: <20200313042527.GA44529@eureka.lemis.com> (raw)
In-Reply-To: <202003130304.02D343ok099975@tahoe.cs.Dartmouth.EDU>
[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]
On Thursday, 12 March 2020 at 23:04:03 -0400, Doug McIlroy wrote:
>> -,: Make the option standard: output numbers with commas every 3 digits
>
> A terrible idea.
Yes, of course. I don't think any of us meant these ideas seriously.
Was this the only objection you had?
> I often do mailx -H | sort -t/ -k2nr to sort in reverse order of size--a
> quick way to find the pay dirt when I want to shrink my mailbox.
> This would never fly if the sizes had commas. (Well, I suppose I
> could add sed s/,//g to the pipeline.)
In fact, at least FreeBSD sort -n handles the numbers quite happily.
I've tried it with 4.4BSD sort, which with a little coaxing builds
under FreeBSD. It doesn't: it apparently sees the , as a delimiter.
The real question is whether a comma is a valid character in an
integer. There are arguments that it should be.
Greg
--
Sent from my desktop computer.
Finger grog@lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 163 bytes --]
next prev parent reply other threads:[~2020-03-13 4:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 3:04 Doug McIlroy
2020-03-13 4:25 ` Greg 'groggy' Lehey [this message]
2020-03-14 2:24 ` Greg A. Woods
2020-03-14 13:08 ` Richard Salz
2020-03-13 19:48 ` Steffen Nurpmeso
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=20200313042527.GA44529@eureka.lemis.com \
--to=grog@lemis.com \
--cc=doug@cs.dartmouth.edu \
--cc=tuhs@tuhs.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.
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 NNTP newsgroup(s).