unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Tomi Ollila <tomi.ollila@iki.fi>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: convert man pages to sphinx
Date: Wed, 05 Mar 2014 20:11:02 +0200	[thread overview]
Message-ID: <m2d2i0jz2h.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <1394031395-8014-1-git-send-email-david@tethera.net>

On Wed, Mar 05 2014, David Bremner <david@tethera.net> wrote:

> This is the first version actually integrated into the build system.
>
> If people think the results are OK, I think we should move merge
> because it has become more difficult than I thought to update the rst
> files from man page changes.
>
> Of course we can/should still fix any glaring problems.

Looks good -- some things that caught my attention..

in doc/Makefile.local

 -include $(dir)/docdeps.mk  -- so that we don't get complaint about missing
  file 

  rm -f $@; gzip --stdout > $@ < $^  -- as -k option is pretty new in gzip
  world (bzip2 & xz  seems to have had it longer (always?))
  The 'rm -f $@' part is modeled after bzip2 manual page where it says
  hard links are broken...

doc/.gitignore  -- is missing, docdeps.mk & _build there

both "make rst2man" and "make sphinx-man SPHINXBUILD=sphinx-1.0-build" seems
to do good job. I happened to notice that one reference to other manual
page was still underlined instead of bolded, manually checking 
the output of grep -n '([0-9])' **/*.rst indicates that the one in
man1/notmuch.rst:88: is (probably) the only one.


Tomi


>
> One thing that is not here at all is any kind of automation of the
> fallback for people without (recent) sphinx.
>
> I also left the nroff man sources in the tree, but if I merge this series 
> (or something similar) I plan to delete them.

  parent reply	other threads:[~2014-03-05 18:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-05 14:56 convert man pages to sphinx David Bremner
2014-03-05 14:56 ` [PATCH 1/4] doc: convert sphinx based docs David Bremner
2014-03-05 14:56 ` [PATCH 2/4] doc: add target rst2man to build man pages using rst2man David Bremner
2014-03-05 14:56 ` [PATCH 3/4] doc: install sphinx version of man pages David Bremner
2014-03-05 14:56 ` [PATCH 4/4] doc: automagically read version from file David Bremner
2014-03-05 18:11 ` Tomi Ollila [this message]
2014-03-06 13:20   ` Sphinx man pages, round n+2 David Bremner
2014-03-06 13:20     ` [PATCH v2 1/4] doc: convert sphinx based docs David Bremner
2014-03-06 13:20     ` [PATCH v2 2/4] doc: add target rst2man to build man pages using rst2man David Bremner
2014-03-06 13:20     ` [PATCH v2 3/4] doc: install sphinx version of man pages David Bremner
2014-03-06 13:20     ` [PATCH v2 4/4] doc: automagically read version from file David Bremner
2014-03-07 12:02     ` Sphinx man pages, round n+2 Tomi Ollila

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=m2d2i0jz2h.fsf@guru.guru-group.fi \
    --to=tomi.ollila@iki.fi \
    --cc=david@tethera.net \
    --cc=notmuch@notmuchmail.org \
    /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).