From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Subject: install info docs v1
Date: Mon, 21 May 2018 13:08:48 -0700 [thread overview]
Message-ID: <20180521200856.17103-1-david@tethera.net> (raw)
I was recently reminded we still don't install the info docs for
notmuch-emacs, so I set out to remedy that. The other issue is that
the notmuch-emacs docs are not very good. I found somethings that I
thought would be simple to be rather frustrating in trying to update
notmuch-emacs.rst. That could well just be a lack of fluency in rst on
my part. I did wonder if maybe we should consider using some sphinx
extension for elisp. I didn't find a well maintained and widely
distributed one. sphinxcontrib-emacs apparently doesn't support
python3 which is a blocker for me. flycheck embeds an extension [1] that
looks fairly nice. It's GPL3+ so we would in principle fork/embed it.
[1]: https://github.com/flycheck/flycheck/blob/master/doc/elisp.py
next reply other threads:[~2018-05-21 20:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 20:08 David Bremner [this message]
2018-05-21 20:08 ` [PATCH 1/8] configure: check for makeinfo and install-info David Bremner
2018-05-26 15:56 ` David Bremner
2018-05-21 20:08 ` [PATCH 2/8] configure: set 'infodir' David Bremner
2018-05-21 20:08 ` [PATCH 3/8] doc: install build and install info pages David Bremner
2018-05-21 20:08 ` [PATCH 4/8] doc: install info files in elpa package David Bremner
2018-05-21 20:08 ` [PATCH 5/8] debian: install info pages as part of elpa-emacs David Bremner
2018-05-21 22:23 ` Tomi Ollila
2018-05-21 20:08 ` [PATCH 6/8] doc: initial documentation for notmuch-show-mode David Bremner
2018-05-21 20:08 ` [PATCH 7/8] doc: initial documentation for notmuch-tree mode David Bremner
2018-05-21 20:08 ` [PATCH 8/8] docs: add initial documentation for notmuch-tag-jump 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=20180521200856.17103-1-david@tethera.net \
--to=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).