From: Kristaps Dzonsons <kristaps@bsd.lv>
To: tech@mdocml.bsd.lv
Subject: Re: Showing all possible apropls keys.
Date: Tue, 22 Nov 2011 09:58:46 +0100 [thread overview]
Message-ID: <4ECB6446.4090201@bsd.lv> (raw)
In-Reply-To: <20111121223702.GA22285@iris.usta.de>
>> Enclosed is a patch to show all possible apropos keys with apropos
>> -k. I chose "-k" more or less arbitrarily.
>>
>> Thoughts?
>
> I think that shouldn't go in.
> This information doesn't belong into the program, but into the manual.
>
> Usage() as a reaction to an unsupported option is ok, but any
> additional user documentation in a program is seriously misplaced.
> Well, maybe with the exception of programs intended for use in an
> environment where man(1) is not available, like fdisk(8) in an
> installation ramdisk.
Ingo,
I'm also more comfortable with this being in the manual -- the patch
came about in my hesitation on just how to encode the information in a
meaningful way, where there's bound to be many possibilities that might
overwhelm the user for such a simple utility.
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?
Kristaps
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2011-11-22 8:58 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 [this message]
2011-11-26 12:21 ` Ingo Schwarze
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=4ECB6446.4090201@bsd.lv \
--to=kristaps@bsd.lv \
--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).