From: Kristaps Dzonsons <kristaps@bsd.lv>
To: discuss@mdocml.bsd.lv
Subject: Library manpages per-function or per-library?
Date: Wed, 12 Nov 2014 15:28:30 +0100 [thread overview]
Message-ID: <54636E8E.3010007@bsd.lv> (raw)
Hi folks,
I thought I'd put this question up for future searches, as it confuses
me and no doubt confuses others, as well. In short, when writing a
library, does one document each function in a separate mdoc(7) page, or
all functions in one big one? Or perhaps, grouped by utility? Or
grouped by header file?
Longer story: I'm writing a library for plotting using cairo. I use it
for my own affairs and it has one big manpage. However, I'm getting
really tired of jumping around in that manpage.
What I think I'd like to do is break it down like pthread(3) or MPI(3),
where there's a page roughly describing the whole library, then each
function gets its own page. (I'd put synonyms on the same page.) This,
to me, makes a lot of sense. One has a general walk-through of all
functions, perhaps grouped in some way, then each function has its own
manpage for later usage.
Any thoughts?
Best,
Kristaps
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next reply other threads:[~2014-11-12 14:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 14:28 Kristaps Dzonsons [this message]
2014-11-12 14:51 ` Joerg Sonnenberger
2014-11-20 2:02 ` Ingo Schwarze
2014-11-20 2:10 ` Guy Harris
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=54636E8E.3010007@bsd.lv \
--to=kristaps@bsd.lv \
--cc=discuss@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).