From: Kristaps Dzonsons <kristaps@bsd.lv>
To: "discuss@mdocml.bsd.lv" <discuss@mdocml.bsd.lv>
Subject: manpages resources
Date: Thu, 03 Jun 2010 12:24:03 +0200 [thread overview]
Message-ID: <4C0782C3.1020106@bsd.lv> (raw)
During m2k10, Joerg, Ingo, and myself discussed putting together a
resource for -mdoc. Cause right now, searching for "writing UNIX
manuals" pulls down a lot of crap. It's no wonder the ports manuals are
such garbage.
So I propose:
http://manpages.bsd.lv/
Try asking about mdoc on the groff list (see the archive for a record of
my questions, most of which were unanswered). They just don't know.
Well we can do better. To this extent I humbly ask that at least the
main authorities---jmc, wiz, ruslan (who's not subscribed here),
etc.---subscribe themselves. To provide at least a single-point for
contact, questions, etc.
I put up a few tutorials on things I find relevant. If anyboby else
would like to contribute (please?), let me know and I can arrange an
account.
Ok, so it's a little kitschy to write a page in mdoc. I got carried away...
Thanks,
Kristaps
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next reply other threads:[~2010-06-03 10:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 10:24 Kristaps Dzonsons [this message]
2010-06-03 15:22 ` Jason McIntyre
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=4C0782C3.1020106@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).