unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Jameson Graef Rollins <jrollins@finestructure.net>
To: David Bremner <bremner@unb.ca>, Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: have "notmuch help" call man?
Date: Fri, 16 Dec 2011 13:35:07 -0800	[thread overview]
Message-ID: <87wr9wgpys.fsf@servo.finestructure.net> (raw)
In-Reply-To: <87zkescxp5.fsf@zancas.localnet>

[-- Attachment #1: Type: text/plain, Size: 571 bytes --]

On Fri, 16 Dec 2011 12:01:42 -0400, David Bremner <bremner@unb.ca> wrote:
> Currently help strings are compiled into the notmuch binary. This is a
> bit a of pain, since we have the same help text in two places.
> What do you think about having "notmuch help foo" invoke "man
> notmuch-foo" and create appropriate man pages (or links).

Hey, David.  I am absolutely in favor of this idea.  I'm a fan of the
git help interface, so the more we can emulate that, and make it so we
only have to maintain documentation in one place, then that's a huge win
in my mind.

jamie.

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

  parent reply	other threads:[~2011-12-16 21:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-16 16:01 have "notmuch help" call man? David Bremner
2011-12-16 16:41 ` Adam Wolfe Gordon
2011-12-16 18:17 ` Kazuo Teramoto
2011-12-16 21:35 ` Jameson Graef Rollins [this message]
2011-12-17  9:56 ` Tomi Ollila
2011-12-20  4:16 ` David Bremner
2011-12-22  3:43   ` David Bremner
2011-12-22  4:53     ` Jameson Graef Rollins
2011-12-22 10:49       ` David Bremner
2011-12-27  0:35       ` David Bremner
2011-12-29  2:24         ` Austin Clements
2011-12-29 13:11           ` [PATCH v3] notmuch: replace built-in help with exec of man David Bremner
2011-12-29 13:47             ` David Bremner
2011-12-30 18:50             ` Austin Clements
2011-12-31 19:25               ` 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=87wr9wgpys.fsf@servo.finestructure.net \
    --to=jrollins@finestructure.net \
    --cc=bremner@unb.ca \
    --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).