From: David Bremner <david@tethera.net>
To: Tomi Ollila <tomi.ollila@iki.fi>, notmuch@notmuchmail.org
Subject: Re: [PATCH 2/3] man: partial conversion to pod.
Date: Tue, 14 Jan 2014 08:06:40 -0400 [thread overview]
Message-ID: <87d2jukbsf.fsf@zancas.localnet> (raw)
In-Reply-To: <m2mwizoamc.fsf@guru.guru-group.fi>
Tomi Ollila <tomi.ollila@iki.fi> writes:
> IMHO it is good idea to have common format where to produce man, info &
> html files. If we're going to need pandoc then the question of source
> format explodes with choices...
Hi Tomi;
I'm not sure how to interpret this. Are you in favour of using pandoc to
produce documentation? As you say we have more choice about source
format in that case. We could even try producing all of the
notmuch-emacs documentation from the common format (as opposed to just
part of it). On the other hand I guess the dependency would be a problem
for people using old linux distros, not to mention less common choices
like *BSD and OS X.
One thing I haven't tried is generating info/notmuch-emacs.texi from
pod. I guess that would make sense if people felt strongly that one
format for all the docs is a priority. I worry a bit about the two step
pod -> texi -> info conversion process, but it's only a hunch.
d
next prev parent reply other threads:[~2014-01-14 12:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-10 2:22 [RFC patch] emacs: skeleton of texinfo manual for emacs interface david
2013-04-25 1:19 ` Second draft of info manual david
2013-04-25 1:19 ` [RFC Patch v2 1/3] info: start info documentation david
2013-04-25 1:19 ` [RFC Patch v2 2/3] man: partial conversion to pod david
2013-04-25 1:19 ` [RFC Patch v2 3/3] debian: install info files david
2014-01-05 11:39 ` third draft of info manual David Bremner
2014-01-05 11:39 ` [PATCH 1/3] info: start info documentation David Bremner
2014-01-05 11:39 ` [PATCH 2/3] man: partial conversion to pod David Bremner
2014-01-13 21:06 ` Tomi Ollila
2014-01-14 12:06 ` David Bremner [this message]
2014-01-14 12:27 ` Tomi Ollila
2014-01-15 13:08 ` David Bremner
2014-01-15 13:08 ` [Patch v3 1/3] info: start info documentation David Bremner
2014-01-17 15:59 ` Jani Nikula
2014-01-17 16:12 ` Jani Nikula
2014-01-17 19:54 ` David Bremner
2014-01-18 11:06 ` Mark Walters
2014-01-18 12:48 ` Tomi Ollila
2014-01-18 14:52 ` [PATCH] emacs: help: add link to info node Mark Walters
2014-01-15 13:08 ` [Patch v3 2/3] man: partial conversion to pod David Bremner
2014-01-17 16:10 ` Jani Nikula
2014-01-17 20:09 ` David Bremner
2014-01-17 23:35 ` Gregor Zattler
2014-01-18 11:11 ` Mark Walters
2014-01-15 13:08 ` [Patch v3 3/3] debian: install info files David Bremner
2014-01-15 13:16 ` David Bremner
2014-01-05 11:39 ` [PATCH " David Bremner
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d2jukbsf.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
/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://yhetil.org/notmuch.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).