diff options
author | ben <ben@FreeBSD.org> | 2000-07-18 14:41:01 +0000 |
---|---|---|
committer | ben <ben@FreeBSD.org> | 2000-07-18 14:41:01 +0000 |
commit | 112e4eb0d560ae01e3d8038d46af0192bf890a15 (patch) | |
tree | fa4d197e46bfc11c1a64e0aa70fb905f389ad34f /share | |
parent | 0f21f86dbfee6196d6c3f1ee96e6ccf03ed917d1 (diff) | |
download | FreeBSD-src-112e4eb0d560ae01e3d8038d46af0192bf890a15.zip FreeBSD-src-112e4eb0d560ae01e3d8038d46af0192bf890a15.tar.gz |
Define what is meant by `brackets' and `braces'.
Suggested by: grog
Diffstat (limited to 'share')
-rw-r--r-- | share/man/man9/style.9 | 15 |
1 files changed, 13 insertions, 2 deletions
diff --git a/share/man/man9/style.9 b/share/man/man9/style.9 index cadc706..963d3c6 100644 --- a/share/man/man9/style.9 +++ b/share/man/man9/style.9 @@ -91,7 +91,13 @@ Put a single tab character between the and the macro name. If they are an inline expansion of a function, the function is defined all in lowercase, the macro has the same name all in uppercase. If the -macro needs more than a single line, use braces. Right-justify the +macro needs more than a single line, use braces +.Po +.Sq \&{ +and +.Sq \&} +.Pc . +Right-justify the backslashes; it makes it easier to read. If the macro encapsulates a compound statement, enclose it in a .Dq Li do @@ -477,7 +483,12 @@ The usage statement should be structured in the following order: .It Options without operands come first, in alphabetical order, -inside a single set of brackets. +inside a single set of brackets +.Po +.Sq \&[ +and +.Sq \&] +.Pc . .It Options with operands come next, also in alphabetical order, |