From: Kyle Milz <krwmilz@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] man du -s correction diff
Date: Tue, 2 Nov 2021 11:54:25 -0700 [thread overview]
Message-ID: <YYGJYTLRZ6MJzWni@imac.0x30.net> (raw)
In-Reply-To: <4EBE77893E9CE3937BDC099792A210A9@eigenstate.org>
On Tue, Nov 02, 2021 at 12:57:15PM -0400, ori@eigenstate.org wrote:
> Quoth Humm <hummsmith42@gmail.com>:
[...]
> >
> > The top level being each `file` argument, and the values being gotten
> > by descending the hierarchy as always.
> >
> > --
> > Humm
> >
>
> I agree that the current phrasing is a bit confusing.
> What about "for each file" => "for each argument"?
given no markup this seems much better. however the original manual
marks up `file` with .IR, and when viewed with something that
displays that markup differently, it is obvious that `file` means
the final argument of du, as described in the synopsis.
next prev parent reply other threads:[~2021-11-02 19:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 22:46 Kyle Milz
2021-11-01 23:39 ` umbraticus
2021-11-02 16:49 ` Kyle Milz
2021-11-02 4:25 ` Xiao-Yong Jin
2021-11-02 9:30 ` hiro
2021-11-02 10:42 ` Eckard Brauer
2021-11-02 15:57 ` Humm
2021-11-02 16:57 ` ori
2021-11-02 18:54 ` Kyle Milz [this message]
2021-11-02 18:54 ` Eckard Brauer
2021-11-02 19:38 ` ori
2021-11-02 21:53 ` Kyle Milz
2021-11-02 19:22 ` hiro
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=YYGJYTLRZ6MJzWni@imac.0x30.net \
--to=krwmilz@gmail.com \
--cc=9front@9front.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).