From: Ingo Schwarze <firstname.lastname@example.org>
Subject: Re: pod2mdoc, docbook2mdoc
Date: Mon, 31 Mar 2014 22:57:36 +0200 [thread overview]
Message-ID: <20140331205736.GJ31866@iris.usta.de> (raw)
Kristaps Dzonsons wrote on Mon, Mar 31, 2014 at 09:40:10PM +0200:
> Note for those with commit access that the modules are in
> /usr/vhosts/mdocml.bsd.lv/pod2mdoc and so.
Err, not quite, there is a "cvs/" missing in the middle.
The following works (if you have commit access):
cvs co pod2mdoc
cvs co docbook2mdoc
> (The commit hook in CVSROOT should probably be updated to mail
> commits on the new modules...)
The commitinfo/loginfo syntax requires BREs, so there is no support
for '|', so i had to copy the respective lines, but nothing much
is wrong with that, i think.
> Ingo Schwarze wrote:
>> In any case, docbook2mdoc seems much more useful than pod2mdoc,
>> at least in a short-term perspective.
> My general thought on pod2mdoc was to avoid invoking perl(1) just to
> run pod2man(1) in the normal chain of looking at POD documents. I
> also thought that, with a few more pod2mdoc smarts, we'll be able to
> deeply mine those documents with mandocdb. From what I understand,
> they're kinda opaque right now.
All true. I didn't mean to call pod2mdoc useless, no doubt it can
bring us benefits when it will be polished.
What i meant to say is that docbook2mdoc is even better because
it might help people convert man(7) manuals to mdoc(7), thus
thwarting esr's evil plan to migrate the world to DocBook. :-)
To unsubscribe send an email to email@example.com
next prev parent reply other threads:[~2014-03-31 20:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <sfid-H20140330firstname.lastname@example.org>
2014-03-30 18:23 ` Kristaps Dzonsons
2014-03-31 9:09 ` Thomas Klausner
2014-03-31 10:30 ` Kristaps Dzonsons
2014-03-31 16:13 ` Ingo Schwarze
2014-03-31 19:40 ` Kristaps Dzonsons
2014-03-31 20:57 ` Ingo Schwarze [this message]
2014-03-31 21:30 ` Thomas Klausner
2014-03-31 21:54 ` Kristaps Dzonsons
2014-03-31 22:21 ` Ingo Schwarze
2014-03-31 22:31 ` Thomas Klausner
2014-04-03 12:02 ` Kristaps Dzonsons
2014-04-03 12:17 ` Thomas Klausner
2014-04-03 12:33 ` Kristaps Dzonsons
2014-04-03 13:53 ` Ingo Schwarze
2014-04-03 16:51 ` Kristaps Dzonsons
2014-04-03 22:06 ` Thomas Klausner
2014-04-04 13:43 ` Kristaps Dzonsons
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).