From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] ls(1): Make man page synopsis consistent with usage output
Date: Wed, 10 Aug 2022 05:06:59 -0400 [thread overview]
Message-ID: <2C18A2D7D0C57B05121210AFECE9BA95@eigenstate.org> (raw)
In-Reply-To: <YvLfzIpMyL/FezdA@quark.lan>
Quoth Josiah Frentsos <jfrent@tilde.team>:
> diff db27bd5be753519505973cc0226e3a49ef5aa23e uncommitted
> --- a/sys/man/1/ls
> +++ b/sys/man/1/ls
> @@ -5,14 +5,16 @@
> .B ls
> [
> .B -dlmnpqrstuFQT
> +] [
> +.I file ...
> ]
> -.I name ...
> .PP
> .B lc
> [
> .B -dlmnqrstuQT
> +] [
> +.I file ...
> ]
> -.I name ...
> .SH DESCRIPTION
> For each directory argument,
> .I ls
thanks, imported
prev parent reply other threads:[~2022-08-10 9:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 22:29 Josiah Frentsos
2022-08-10 9:06 ` ori [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2C18A2D7D0C57B05121210AFECE9BA95@eigenstate.org \
--to=ori@eigenstate.org \
--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).