From: Steffen Nurpmeso <sdaoden@yandex.com>
To: discuss@mdocml.bsd.lv
Subject: Re: Mdocdate
Date: Tue, 17 Nov 2015 11:35:25 +0100 [thread overview]
Message-ID: <20151117103525.Q90laeaL_%sdaoden@yandex.com> (raw)
In-Reply-To: <20151117091157.GA17501@k8>
Hi!
Svyatoslav Mishyn <juef@openmailbox.org> wrote:
|(Mon, 16 Nov 14:35) Steffen Nurpmeso:
|> ..if someone will write a good markdown to mdoc
|> converter then world dominition is only a small step away.
|
|mkd2man ?
|https://github.com/faelys/libsoldout/blob/trunk/mkd2man.c
Oh, yes that looks pretty cool... It seems it has been turned
from MAN to MDOC on January 12th 2015 thanks to Baptiste Daroussin
of FreeBSD!
Hmm...
|But yes, it needs some enhancements.
Ok. That..seems..to..be....overly true. :)
Well i guess someone had to write a pandoc(1) extension or
something rather likewise. (Not that i know pandoc.)
It supports man(7), which i find unbelievable given that this
format doesn't even support active references. And now they even
use blue font for .. nothing! mdoc(7) can better than that!
Ah i don't know why people don't like this incredibly simple, easy
pars- and understandable documentation format! I always enjoy
glancing over the 9483 self-containing lines of my MUA's manual.
--steffen
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2015-11-17 10:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 9:25 Mdocdate Dag-Erling Smørgrav
2015-11-12 21:31 ` Mdocdate Ingo Schwarze
2015-11-12 23:06 ` Mdocdate Ingo Schwarze
2015-11-13 5:52 ` Mdocdate Dag-Erling Smørgrav
2015-11-14 1:22 ` Mdocdate Ingo Schwarze
2015-11-14 15:02 ` Mdocdate Steffen Nurpmeso
2015-11-15 1:51 ` Mdocdate Ingo Schwarze
2015-11-16 13:35 ` Mdocdate Steffen Nurpmeso
2015-11-17 9:12 ` Mdocdate Svyatoslav Mishyn
2015-11-17 10:35 ` Steffen Nurpmeso [this message]
2015-11-23 20:48 ` Mdocdate Michael Dexter
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=20151117103525.Q90laeaL_%sdaoden@yandex.com \
--to=sdaoden@yandex.com \
--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).