From: Ingo Schwarze <schwarze@usta.de>
To: tech@mdocml.bsd.lv
Subject: Re: Showing all possible apropls keys.
Date: Sat, 26 Nov 2011 13:21:25 +0100 [thread overview]
Message-ID: <20111126122125.GD13912@iris.usta.de> (raw)
In-Reply-To: <4ECB6446.4090201@bsd.lv>
Hi Kristaps,
Kristaps Dzonsons wrote on Tue, Nov 22, 2011 at 09:58:46AM +0100:
> My initial thought, however, was just to cut out parts of your macro
> synopsis documentation for a two-column display, e.g.,
>
> Accepted keywords are as follows:
>
> Nd description of manual page
> Nm name of manual page
> Fn a function name
> ...
>
> Better?
Yes.
I'd probably try to help people by giving acronyms as much as possible,
then pointing to mdoc(7) afterwards. A bit like:
The following search keywords are available:
NAME section content:
Nm name of the manual page (defined in each page)
Nd one-line description (defined in each page)
Information about command line utilities:
Nm name of the command
Fl flag (command line option)
Cm command modifier
Ar argument on the command line
Ic internal or interactive command
Ev environment variable
Pa path name in the file system
Information about function libraries:
Lb library name
In include file
Ft function return type
Fn function name
Fa function argument type and argument name
Vt variable type
Va variable name
Dv defined variable or preprocessor constant
Er error constant
Various information:
An author name
Lk hyperlink
Mt mailto hyperlink
Cd configuration declaration for kernel devices
Ms mathematical symbol
Tn tradename
Physical markup:
Em emphasised text (italic or underlined)
Li literal text (constant width)
Sy symbolic text (bold face)
Section headers and cross references:
Sh section header (standard section headers are not indexed)
Ss subsection header
Xr cross reference to another manual page
Rs reference start (bibliographic block)
St standards reference
At AT&T UNIX version reference
Bx BSD version reference
Bsx BSD/OS version reference
Nx NetBSD version reference
Fx FreeBSD version reference
Ox OpenBSD version reference
Dx DragonFly version reference
These search keywords follow mdoc(7) macro names,
even when the manual page is written using the man(7) language
and even when only a formatted version of the manual is available.
Even in the latter two cases, searching by `Nm' and `Nd' is
possible, but most other search keys are not going to return
the page.
Well, something like that.
Note that in some places, i deliberately chose a different
wording compared to mdoc(7), for two reasons: The audience
is different, people reading apropos(1) will use these keys
less often than people using mdoc(7), so acronyms are more
important. And the purpose is slightly different, people
using apropos(1) just need a rough understanding what the keys
will probably return, while people reading mdoc(7) are manual
authors or maintainers and have to understand some finer points
about when and how to use individual macros.
Yours,
Ingo
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2011-11-26 12:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 17:13 Kristaps Dzonsons
2011-11-21 22:37 ` Ingo Schwarze
2011-11-22 8:58 ` Kristaps Dzonsons
2011-11-26 12:21 ` Ingo Schwarze [this message]
2011-11-28 20:37 ` Kristaps Dzonsons
2011-11-28 23:59 ` Ingo Schwarze
2011-11-29 0:34 ` Kristaps Dzonsons
2011-11-29 1:01 ` Ingo Schwarze
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=20111126122125.GD13912@iris.usta.de \
--to=schwarze@usta.de \
--cc=tech@mdocml.bsd.lv \
/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).