From: Jani Nikula <jani@nikula.org>
To: Jameson Graef Rollins <jrollins@finestructure.net>,
	David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: [PATCH 0/6] notmuch cli config changes
In-Reply-To: <87a9r9o4ks.fsf@servo.finestructure.net>
References: <cover.1359495450.git.jani@nikula.org>
	<871ucts54t.fsf@servo.finestructure.net>
	<87y5f0fhtd.fsf@zancas.localnet>
	<87fw12nf7w.fsf@servo.finestructure.net>
	<87k3qd92sw.fsf@zancas.localnet>
	<87a9r9o4ks.fsf@servo.finestructure.net>
User-Agent: Notmuch/0.14+255~gff3cc55 (http://notmuchmail.org) Emacs/24.2.1
	(x86_64-pc-linux-gnu)
Date: Tue, 12 Feb 2013 22:06:30 +0200
Message-ID: <871ucl70vt.fsf@nikula.org>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: list

On Tue, 12 Feb 2013, Jameson Graef Rollins <jrollins@finestructure.net> wrote:
> But don't get me wrong, the CLI is one of the things that makes notmuch
> so incredibly awesome.  It's an email swiss army knife that's there when
> you need it.  But given that even I often need to look at the man page
> during my occasional CLI usage, I just don't want to see it get to
> overcrowded.

Retrospectively, I observe that my series (up to but not including the
last patch) might help reduce the clutter in the future by facilitating
the move of common options from subcommands to top level. For example,
*all* the options to notmuch new would make (more) sense at the top
level (--verbose, --debug, --no-hooks) and could be useful in other
subcommands.

> In any event, I've certainly said more than my peace on this issue.
> Jani's series looks good to me (although, ironically, it's missing
> documentation updates!).

Heh, I just wanted to see what the response was first before putting in
the effort to document it. The code comes easy. :)

BR,
Jani.