Re: Replacing my name/email with "me" (or similar) in author lists

diff --git a/eb/61b437f3f1e32e3ebd66ffbc68fe10b952be58 b/eb/61b437f3f1e32e3ebd66ffbc68fe10b952be58
new file mode 100644 (file)
index 0000000..9fd983c
--- /dev/null
+++ b/eb/61b437f3f1e32e3ebd66ffbc68fe10b952be58
@@ -0,0 +1,84 @@
+Return-Path: <prvs=3991595b0=jrosenthal@jhu.edu>\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 79273431E82\r
+       for <notmuch@notmuchmail.org>; Wed, 29 Feb 2012 07:50:21 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -2.3\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5\r
+       tests=[RCVD_IN_DNSWL_MED=-2.3] 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 Av0loqmBs0ij for <notmuch@notmuchmail.org>;\r
+       Wed, 29 Feb 2012 07:50:21 -0800 (PST)\r
+Received: from ipex2.johnshopkins.edu (ipex2.johnshopkins.edu [162.129.8.151])\r
+       (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id DF3DD431E64\r
+       for <notmuch@notmuchmail.org>; Wed, 29 Feb 2012 07:50:20 -0800 (PST)\r
+X-IronPort-AV: E=Sophos;i="4.73,503,1325480400"; d="scan'208";a="129588587"\r
+Received: from unknown (HELO watt) ([10.161.33.18])\r
+       by ipex2.johnshopkins.edu with ESMTP/TLS/AES256-SHA;\r
+       29 Feb 2012 10:50:20 -0500\r
+Received: from jkr by watt with local (Exim 4.76)\r
+       (envelope-from <jrosenthal@jhu.edu>)\r
+       id 1S2lni-0006Pw-Fb; Wed, 29 Feb 2012 10:50:46 -0500\r
+From: Jesse Rosenthal <jrosenthal@jhu.edu>\r
+To: Austin Clements <amdragon@MIT.EDU>\r
+Subject: Re: Replacing my name/email with "me" (or similar) in author lists\r
+In-Reply-To: <20120229153657.GA772@mit.edu>\r
+References: <slrnjki3c7.tcm.quite@kelebek.lublin.se>\r
+       <20120226112210.5422.8471@brick.lan>\r
+       <87ehthfsyn.fsf@schoepe.localhost> <87fwdxk062.fsf@zancas.localnet>\r
+       <87ehth8dd2.fsf@hermes.hocat.ca> <878vjl3ck3.fsf@jhu.edu>\r
+       <20120229153657.GA772@mit.edu>\r
+User-Agent: Notmuch/0.11.1+192~g36ce7e3 (http://notmuchmail.org)\r
+       Emacs/24.0.93.1 (i686-pc-linux-gnu)\r
+Date: Wed, 29 Feb 2012 10:50:46 -0500\r
+Message-ID: <877gz5tz8p.fsf@jhu.edu>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+Cc: Notmuch Mail <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, 29 Feb 2012 15:50:21 -0000\r
+\r
+On Wed, 29 Feb 2012 10:36:57 -0500, Austin Clements <amdragon@MIT.EDU> wrote:\r
+> What if the output of search (say, specifically the JSON format)\r
+> included information on each message in the thread such as the\r
+> 'message' production from devel/schemata minus the body field?  Then\r
+> the frontend would have loads of information it could produce its own\r
+> summaries from.  (Plus, with a little tweaking, I don't think this\r
+> would be any more expensive than producing the current notmuch search\r
+> summary output.)\r
+\r
+I was hoping for something like that when I started fiddling. But it's\r
+still going to end up being a library question, because\r
+notmuch-search.c, is tied pretty tightly to the lib: i.e. it uses\r
+functions like `notmuch_thread_get_authors (thread)'. I was using the\r
+python bindings, and I ended up having to make a second query off the\r
+thread id (I could have recursed through the messages too, I suppose).\r
+\r
+So I guess what I'm saying is that what you're suggesting sounds great,\r
+but we'd still have to either (a) add new library functions\r
+(`notmuch_thread_get_recipients', `notmuch_thread_abbrev_me'), (b) keep\r
+them all in the client and make pazz and scripters recreate them, or (c)\r
+play around in the sort of client-library space that it sounded like\r
+Bremner was suggesting.\r
+\r
+Best,\r
+Jesse\r
+\r