From: Isaac Dunham <idunham@lavabit.com>
To: musl@lists.openwall.com
Subject: Re: documenting musl
Date: Sat, 8 Sep 2012 07:24:09 -0700 [thread overview]
Message-ID: <20120908072409.1c8e0157@newbook> (raw)
In-Reply-To: <20120908124723.GA68331@intma.in>
On Sat, 8 Sep 2012 08:47:23 -0400
Kurt H Maier <khm-lists@intma.in> wrote:
> On Sat, Sep 08, 2012 at 02:35:22PM +0200, Daniel Cegiełka wrote:
> > 2012/9/8 Kurt H Maier <khm-lists@intma.in>:
> > > On Sat, Sep 08, 2012 at 10:44:03AM +0200, Daniel Cegiełka wrote:
> > >> btw. documentation - mandoc is a better option than
> > >> (old/big/ugly) groff for documentation.
> > >
> > > None of those links explain why they seem to think it's either
> > > groff or roll-your-own, when there are plenty of lightweight roff
> > > implementations. Any hints?
> >
> > hmm... mandoc isn't lightweight? :)
> >
No, but it's not roff.
Yes, I use roff to write regular documents.
AFAICT if you want any old-format or portable manpages to work, you
may need groff anyhow (unsupported macros make it fallback to groff)
> >
> > Daniel
>
> Now you're doing it. There are dozens of other roff implementations,
> such as the one that comes with 9base, or the heirloom doctools, etc.
> Why does everyone who uses mandoc ignore everything but groff?
I'm using heirloom troff myself, and if I write the docs to use *roff
& kin, they will work with heirloom troff (though I _don't_ plan to
make it specific to heirloom-doctools).
Now that may require a little bit of hacking on their mandoc support
if you want mandoc format. Several mandoc format pages, such as pcc.1,
don't work properly there.
next prev parent reply other threads:[~2012-09-08 14:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-08 2:40 Rich Felker
2012-09-08 6:36 ` Isaac Dunham
2012-09-08 8:44 ` Daniel Cegiełka
2012-09-08 11:48 ` Kurt H Maier
2012-09-08 12:35 ` Daniel Cegiełka
2012-09-08 12:46 ` Rich Felker
2012-09-08 12:53 ` Daniel Cegiełka
2012-09-08 12:47 ` Kurt H Maier
2012-09-08 13:12 ` Daniel Cegiełka
2012-09-08 13:16 ` Kurt H Maier
2012-09-08 13:42 ` Daniel Cegiełka
2012-09-08 14:09 ` Kurt H Maier
2012-09-09 1:43 ` John Spencer
2012-09-08 14:24 ` Isaac Dunham [this message]
2012-09-08 15:07 ` Isaac Dunham
2012-09-08 19:46 ` Szabolcs Nagy
2012-09-08 11:44 ` Justin Cormack
2012-09-08 14:53 ` Isaac Dunham
2012-09-09 3:09 ` nwmcsween
2012-09-09 4:15 ` Rich Felker
2012-09-09 4:15 ` nwmcsween
2012-09-09 6:12 ` Rich Felker
2012-09-09 8:04 ` Justin Cormack
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=20120908072409.1c8e0157@newbook \
--to=idunham@lavabit.com \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).