9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Kyle Milz <krwmilz@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] man du -s correction diff
Date: Tue, 2 Nov 2021 14:53:27 -0700	[thread overview]
Message-ID: <YYGzV0jUcwMb9j+4@imac.0x30.net> (raw)
In-Reply-To: <64533601D12D22872A99F2CD9C550F23@eigenstate.org>

On Tue, Nov 02, 2021 at 03:38:10PM -0400, ori@eigenstate.org wrote:
> A bunch of tweaks.

looks like we almost wrote the same diff..

comments inline.

> diff ca73f673473457152d6f1b2e9030495f8dec5c49 uncommitted
> --- a//sys/man/1/du
> +++ b//sys/man/1/du
> @@ -35,60 +35,53 @@
>  The count for a directory includes the counts of the
>  contained files and directories.
>  .PP
> -The
> +The following options are accepted:
> +.TP
>  .B -a
> -option prints the number of blocks
> -for every file in a directory.
> +Print the number of blocks for every file in a directory.
>  Normally counts are printed only for contained directories.
> -.PP
> -The
> +.TP
>  .B -f
> -option suppresses the printing of warning messages.
> -.PP
> -The
> +Suppresses the printing of warning messages.

use present tense 'Supress' to match the other options?

> +.TP
>  .B -n
> -option prints the size in bytes and the name of each file; it sets
> +Print the size in bytes and the name of each file; it sets
>  .BR -a .
> -.PP
> -The
> +.TP
>  .B -t
> -option prints, in the format of
> +Print, in the format of
>  .B du
>  .BR -n ,
> -the modified time of
> -each file rather than the size.
> +the modified time of each file rather than the size.
>  If the options
>  .B -tu
>  are specified then the accessed time is printed.
> -.PP
> -The
> +.TP
>  .B -q
> -option prints, in the format of
> +Print, in the format of
>  .B du
>  .BR -n ,
>  the QID path of
>  each file rather than the size.
> -.PP
> -The
> +.TP
>  .B -s
> -option causes
> +Causes

i dont think 'Causes du to...' adds any value. i think we can assume the
reader knows that options are going to change a programs behavior.

>  .I du
>  to descend the hierarchy as always, but to print only a summary line
>  for each
> -.IR file .
> -.PP
> -The
> +.I file 
> +argument.
> +.TP

yes

>  .B -e
> -option causes
> +Causes

same as above

>  .I du
>  to print values (sizes, times or QID paths)
>  in `scientific notation' via
>  .IR print (2)'s
>  .BR %g .
> -.PP
> -The
> +.TP
>  .B -h
> -option causes
> +Causes

same as above

>  .I du
>  to print values (sizes, times or QID paths)
>  in scientific notation,
> @@ -96,10 +89,9 @@
>  (e.g.,
>  .L G
>  for binary gigabytes).
> -.PP
> -The
> +.TP
>  .B -p
> -option causes
> +Causes

same as above 

>  .I du
>  to print values (sizes, times or QID paths)
>  in units of
> @@ -109,12 +101,6 @@
>  An empty
>  .IR SI-prefix
>  corresponds to a scale factor of 1 (e.g., print sizes in bytes).
> -.\" .PP
> -.\" The
> -.\" .B -r
> -.\" option causes
> -.\" .I du
> -.\" to read and discard every byte of every file encountered.

hmm, this is actually supported by the source code, although it says
its undocumented. i'm inclined to leave it here, commented,
but dont feel strongly.

>  .SH EXAMPLES
>  Print the size of
>  .L /tmp
> 

  reply	other threads:[~2021-11-03  2:55 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
2021-11-02 18:54     ` Eckard Brauer
2021-11-02 19:38       ` ori
2021-11-02 21:53         ` Kyle Milz [this message]
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=YYGzV0jUcwMb9j+4@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).