--- /dev/null
+Return-Path: <wking@tremily.us>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by olra.theworths.org (Postfix) with ESMTP id 6AD64431FBD\r
+ for <notmuch@notmuchmail.org>; Wed, 23 Apr 2014 08:46:56 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.1\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5\r
+ tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,\r
+ RCVD_IN_DNSWL_NONE=-0.0001] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+ by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id DGOF0eqg7fa6 for <notmuch@notmuchmail.org>;\r
+ Wed, 23 Apr 2014 08:46:49 -0700 (PDT)\r
+Received: from QMTA11.westchester.pa.mail.comcast.net\r
+ (qmta11.westchester.pa.mail.comcast.net [76.96.59.211])\r
+ by olra.theworths.org (Postfix) with ESMTP id 652EA431FAE\r
+ for <notmuch@notmuchmail.org>; Wed, 23 Apr 2014 08:46:49 -0700 (PDT)\r
+Received: from omta02.westchester.pa.mail.comcast.net ([76.96.62.19])\r
+ by QMTA11.westchester.pa.mail.comcast.net with comcast\r
+ id tPUs1n0010QuhwU5BTmp26; Wed, 23 Apr 2014 15:46:49 +0000\r
+Received: from odin.tremily.us ([24.18.63.50])\r
+ by omta02.westchester.pa.mail.comcast.net with comcast\r
+ id tTkm1n01A152l3L3NTkndJ; Wed, 23 Apr 2014 15:44:49 +0000\r
+Received: by odin.tremily.us (Postfix, from userid 1000)\r
+ id 46014116ABBF; Wed, 23 Apr 2014 08:44:46 -0700 (PDT)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tremily.us; s=odin;\r
+ t=1398267886; bh=jMOvi8hUVhTap1dDq1Npcz4LVMnt67xOF8IYYpvEK+o=;\r
+ h=Date:From:To:Cc:Subject:References:In-Reply-To;\r
+ b=Gb7ooAIxZAu/XnAOtWmFJifc820te/QZt2/YfJenvX3zGqOf03dLmXmnKwdznsk5S\r
+ jmoKMWT/7DNxigFANZURpQJIiKQvkQaH7FgylMb2iEVN+ANGMljnNSOUfpnpmGoTXt\r
+ 7FgWbG7oNcGQ1p4Ub1aLUJ9llfab0+GoJ4ZnlNpA=\r
+Date: Wed, 23 Apr 2014 08:44:46 -0700\r
+From: "W. Trevor King" <wking@tremily.us>\r
+To: Carl Worth <cworth@cworth.org>\r
+Subject: Re: Thanks for the nmbug-status program\r
+Message-ID: <20140423154445.GN9243@odin.tremily.us>\r
+References: <87eh0prrup.fsf@yoom.home.cworth.org>\r
+ <20140422213442.GI9243@odin.tremily.us>\r
+ <8761m1rmtp.fsf@yoom.home.cworth.org>\r
+ <20140423001824.GM9243@odin.tremily.us>\r
+ <87wqegr3dm.fsf@yoom.home.cworth.org>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/signed; micalg=pgp-sha1;\r
+ protocol="application/pgp-signature"; boundary="j1Wwy33+dU2Jf0xa"\r
+Content-Disposition: inline\r
+In-Reply-To: <87wqegr3dm.fsf@yoom.home.cworth.org>\r
+OpenPGP: id=39A2F3FA2AB17E5D8764F388FC29BDCDF15F5BE8;\r
+ url=http://tremily.us/pubkey.txt\r
+User-Agent: Mutt/1.5.23 (2014-03-12)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net;\r
+ s=q20140121; t=1398268009;\r
+ bh=zGFZ3ty7gX81yeOj8me8e+pfN01c696oQBaT9EFALdo=;\r
+ h=Received:Received:Received:Date:From:To:Subject:Message-ID:\r
+ MIME-Version:Content-Type;\r
+ b=cyHclQHcBvZl0UE1fWMRUZeyRqT3TMUCT+4oDu5PR069O8QprAf1vMyr5iRLortzC\r
+ s/cex9Bqd+ADrJDzOOs28I/r2SO6JEbZKo02QOqmISoXwG3xJrS16kSBLRDgyF3SIv\r
+ qxQeugyAwwk+CMOmUi8/JvYdqUm5Bazvz802ndebDS4YpCQ+fR/EDelDNq7S4YbxOr\r
+ zqhjWlxnY+bM7b0EvYhmlJwgSxCC5rbR5ACu4kykDvTFkcygfSKKIPYtYt35CU3GJ2\r
+ NjYGddkkvHubiw4+xapTjhBQmQjSeJiXZ+utpd6+hePP8xLft5AqW5xuodRWfilMIh\r
+ AHOlGOcFQYOxw==\r
+Cc: Notmuch List <notmuch@notmuchmail.org>\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Wed, 23 Apr 2014 15:46:56 -0000\r
+\r
+\r
+--j1Wwy33+dU2Jf0xa\r
+Content-Type: text/plain; charset=utf-8\r
+Content-Disposition: inline\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+On Tue, Apr 22, 2014 at 11:01:09PM -0700, Carl Worth wrote:\r
+> W. Trevor King writes:\r
+> >> > I think that making nmbug and nmbug-status generally applicable\r
+> >> > for other projects is a good target. I don't see any need to\r
+> >> > pull them out into a stand-alone project to do that though.\r
+> >>=20\r
+> >> For what it's worth, I don't disagree.\r
+> >\r
+> > Does that mean your patches are aimed upstream at the notmuch\r
+> > repository?\r
+>=20\r
+> I didn't really intend them that way. What I meant was that I'd be\r
+> happy to switch to a script within the notmuch repository if it did\r
+> what I wanted, (which is basically just "create an HTML file from a\r
+> notmuch query").\r
+\r
+So, =E2=80=9Chere's a goal to shoot for, and I'm happy with my fork. If\r
+someone else wants to land patches like these upstream, I'm also happy\r
+dropping my fork.=E2=80=9D ;). I think it would be easier to just mail your\r
+patches to the list and see what sticks.\r
+\r
+> > (or their shell's approriate environment variable syntax), and I'd\r
+> > version the config file in the same repo as the associated tags. I\r
+> > don't see the point of keeping the config file somewhere else, when\r
+> > you'll already need a repository to store the tags.\r
+>\r
+> Ah, then you've missed something different about my usage. I don't\r
+> have any repository storing tags. My tags exist only in my notmuch\r
+> database.\r
+\r
+I had missed that, thanks for clarifying. I still like the\r
+config-from-repository-branch functionality because nmbug tag\r
+repositories are part of the nmbug-status ecosystem, but I agree that\r
+you shouldn't need a tag repository if you don't want to collaborate\r
+on tag maintenance.\r
+\r
+> > * d456390 Add a comment describing the program\r
+> >\r
+> > I like the idea, but I'd prefer a docstring just after the leading\r
+> > comment. Then we could reuse the docstring as the description for\r
+> > the ArgumentParser.\r
+>=20\r
+> Sure. That's better.\r
+\r
+Would you like to write that up?\r
+\r
+> > * 336411f Add "notmuch search" to the advertised queries.\r
+> >\r
+> > Folks can already copy-paste the terms into Emacs etc. You only\r
+> > need the 'notmuch search' prefix if you're pasting into a shell,\r
+> > in which case you'll also want to escape shell-sensitive\r
+> > characters like parenthesis. I'm fine without this one.\r
+>=20\r
+> This is more about advertising notmuch to people not familiar with\r
+> it. It's more important for something like "mesa stable queue" than\r
+> it is for the notmuch bug list, of course.\r
+\r
+That makes sense, but I'd prefer something like:\r
+\r
+ <p>This view is generated from the following\r
+ <a href=3D"http://notmuchmail.org/searching/">Notmuch query</a>:\r
+ </p>\r
+ <p>\r
+ <code>\r
+ view['query-string']\r
+ </code>\r
+ </p>\r
+\r
+That name-drops Notmuch without implying that the whole thing is\r
+copy-pastable into a shell. Neither your queries [1] nor our\r
+nmbug-status queries [2] use parens at the moment, but the current\r
+master's example config does [3].\r
+\r
+> > * 396869c Add support for a --query option (along with a default config=\r
+uration)\r
+> >\r
+> > I don't have an opinion about this one ;). The default config doesn't\r
+> > look very useful (especially with it's dummy metadata settings), but\r
+> > I'd only be using the in-Git-config approach, and I don't mind if\r
+> > others want something like this.\r
+>=20\r
+> This is about making this script self-documenting.\r
+>=20\r
+> When I first tried nmbug-status I got just a stack trace[*], not even a\r
+> usage message.\r
+\r
+Heh, that should probably be fixed ;). There's a nice example config\r
+at devel/nmbug/status-config.json, but something that's bound more\r
+tightly to the script itself seems useful.\r
+\r
+> Even after running "nmbug-status --help" I wasn't any closer to\r
+> knowing how to run the thing. It wasn't obvious that --config was\r
+> the option I needed to get things to work, (from the stack trace,\r
+> clearly this script wants some git repository somewhere), and even\r
+> if I had know that --config was what I wanted, I had no idea how to\r
+> construct a config file.\r
+\r
+I hadn't understood that your built-in config was more of a\r
+teaser/seed for new users, it makes more sense in that light. I'd\r
+prefer a clearer error message when we can't find a config file (I'm\r
+working up a patch now ;), and documentation for the config file\r
+format in 'nmbug-status --help' (where it's clearly static assistence\r
+for unfamiliar users).\r
+\r
+Cheers,\r
+Trevor\r
+\r
+[1]: http://cworth.org/~cworth/mesa-stable-queue/\r
+[2]: http://nmbug.tethera.net/status/\r
+[3]: http://git.notmuchmail.org/git/notmuch/blob/40dc79d6ac828bc24ae1ec797a=\r
+a50e53fc455621:/devel/nmbug/status-config.json#l65\r
+\r
+--=20\r
+This email may be signed or encrypted with GnuPG (http://www.gnupg.org).\r
+For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy\r
+\r
+--j1Wwy33+dU2Jf0xa\r
+Content-Type: application/pgp-signature; name="signature.asc"\r
+Content-Description: OpenPGP digital signature\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v2.0.22 (GNU/Linux)\r
+\r
+iQIcBAEBAgAGBQJTV9/rAAoJEKKfehoaNkbtASwP/jgLDvQxgP0MB+DDbM1DrdtD\r
+yj0kzbuCZWUmXBeMFvEllfEXaySDhR5Q38N7ZL0rZhAQRYwif+a63MworaCFk6VB\r
+u4u4DlyJR0nj1o2mNjGTugv5x/aOUm4T1RTklJ5+v214LfBFKBVAtWqxU+AUglz/\r
+JFa23PZNiJ/CFmvxpPnxJ4GD8EHlaRUUikOPIrP1h9RFga5XYhPLagu9shYX5pOB\r
+Udao6NOoLftiHxioyT9SBc9CYNTAb9F9jBtJ1uvLG3HBxVwqgaxE1rbqersOU26a\r
+MPQU57yGvKzungJIgdkpydGDwmmO7Uc6tVNpBvwvAuHswFzn4X3NQtwmZ0DbW6Fu\r
+p0lrEyEEeurXo1nFDbObIKmxyC0wWcF9CzRKsakBHTYHxkZjxKCV3kOwv+E50Pbf\r
+AoRON3BaLIQzLfxQn+Rq/KyxMQG7+yQZfwaQC7mb759qUvxY/8CE66EAwxrzDBtY\r
+QhXNs1YT4YGeXxRvZkXe2QWYBFC+9lQ1i4xp5vHi+4rDCM8VwqJLfE6Qi+9nlZr1\r
+w+OsNs5u5+Dfe71/Avw/gMpbvi4Raw3fhMEP5OX6cMHs1ouhi8UxONe7Md/4IO5g\r
+KU09R070phMhdUintd+q+zV4S8ubuOd5UOQaRXLWjHpz3Gdv/5/jblkwhhsUTrJP\r
+4IdPXNXIWH1OuEJJReyG\r
+=EZAK\r
+-----END PGP SIGNATURE-----\r
+\r
+--j1Wwy33+dU2Jf0xa--\r