* [9front] Tar's usage messages
@ 2020-12-13 7:47 kl
2020-12-13 8:04 ` Kurt H Maier
0 siblings, 1 reply; 3+ messages in thread
From: kl @ 2020-12-13 7:47 UTC (permalink / raw)
To: 9front
Hi,
How should I read this,
tar {crtx}[PRTfgkmpuvz] [archive] file1 file2...
Is there any document out there which describes the conventions for
documenting command line arguments?
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [9front] Tar's usage messages
2020-12-13 7:47 [9front] Tar's usage messages kl
@ 2020-12-13 8:04 ` Kurt H Maier
2020-12-13 14:36 ` Stuart Morrow
0 siblings, 1 reply; 3+ messages in thread
From: Kurt H Maier @ 2020-12-13 8:04 UTC (permalink / raw)
To: 9front
On Sun, Dec 13, 2020 at 01:47:19PM +0600, kl wrote:
> Hi,
>
> How should I read this,
>
>
> tar {crtx}[PRTfgkmpuvz] [archive] file1 file2...
>
>
>
> Is there any document out there which describes the conventions for
> documenting command line arguments?
There is no central rulebook for usage messages; each program must print
its own. Generally, elements in square brackets are optional arguments,
and elements without them are required. In tar(1)'s case the {crtx}
section indicates that you may have at most one function. Usually it is
advisable to consult the manpage if the printed usage message isn't
helpful enough.
khm
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-12-13 14:38 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-12-13 7:47 [9front] Tar's usage messages kl
2020-12-13 8:04 ` Kurt H Maier
2020-12-13 14:36 ` Stuart Morrow
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).