Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 3DDE7431E82 for ; Wed, 29 Feb 2012 07:37:04 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.7 X-Spam-Level: X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FzRtrlkcUNbv for ; Wed, 29 Feb 2012 07:37:03 -0800 (PST) Received: from dmz-mailsec-scanner-3.mit.edu (DMZ-MAILSEC-SCANNER-3.MIT.EDU [18.9.25.14]) by olra.theworths.org (Postfix) with ESMTP id 99739431E64 for ; Wed, 29 Feb 2012 07:37:03 -0800 (PST) X-AuditID: 1209190e-b7f7c6d0000008c3-64-4f4e461ff807 Received: from mailhub-auth-3.mit.edu ( [18.9.21.43]) by dmz-mailsec-scanner-3.mit.edu (Symantec Messaging Gateway) with SMTP id 54.47.02243.F164E4F4; Wed, 29 Feb 2012 10:37:03 -0500 (EST) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id q1TFb2Q4010113; Wed, 29 Feb 2012 10:37:02 -0500 Received: from awakening.csail.mit.edu (awakening.csail.mit.edu [18.26.4.91]) (authenticated bits=0) (User authenticated as amdragon@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id q1TFaw04027393 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 29 Feb 2012 10:37:01 -0500 (EST) Received: from amthrax by awakening.csail.mit.edu with local (Exim 4.77) (envelope-from ) id 1S2laL-000840-Vd; Wed, 29 Feb 2012 10:36:58 -0500 Date: Wed, 29 Feb 2012 10:36:57 -0500 From: Austin Clements To: Jesse Rosenthal Subject: Re: Replacing my name/email with "me" (or similar) in author lists Message-ID: <20120229153657.GA772@mit.edu> References: <20120226112210.5422.8471@brick.lan> <87ehthfsyn.fsf@schoepe.localhost> <87fwdxk062.fsf@zancas.localnet> <87ehth8dd2.fsf@hermes.hocat.ca> <878vjl3ck3.fsf@jhu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <878vjl3ck3.fsf@jhu.edu> User-Agent: Mutt/1.5.21 (2010-09-15) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprBKsWRmVeSWpSXmKPExsUixCmqrSvv5udv8KGX3eJGazejxbetuxkt rt+cyWxxf+8CdgcWj3/fvrN7PFt1i9ljy6H3zB4THs9nCmCJ4rJJSc3JLEst0rdL4Mp4ceUs U8E79oojG7vYGxhXsHUxcnJICJhIrHi2F8oWk7hwbz2QzcUhJLCPUeLWif9MIAkhgQ2MEnOX B0IkTjJJPJvQBlW1hFGi58cFsCoWAVWJhy+PsoPYbAIaEtv2L2cEsUWA7AVt68DizAI1Erv6 zoLFhQW8JbqvLAXr5RXQkjiw4zczxNCHjBKrPs1khkgISpyc+YQFollL4sa/l0ANHEC2tMTy fxwgYU6gvZueN7CC2KICKhJTTm5jm8AoNAtJ9ywk3bMQuhcwMq9ilE3JrdLNTczMKU5N1i1O TszLSy3SNdbLzSzRS00p3cQIjgBJvh2MXw8qHWIU4GBU4uGV5Pf1F2JNLCuuzD3EKMnBpCTK 2+Xi5y/El5SfUpmRWJwRX1Sak1p8iFGCg1lJhPetFFCONyWxsiq1KB8mJc3BoiTOq6b1zk9I ID2xJDU7NbUgtQgmK8PBoSTBa+MK1ChYlJqeWpGWmVOCkGbi4AQZzgM03Bukhre4IDG3ODMd In+KUVFKnNcWJCEAksgozYPrhSWoV4ziQK8I82qDVPEAkxtc9yugwUxAgwM4vUEGlyQipKQa GBMSzGNPrVCQXNSn+ShBzOJnfvv0VW7FMmz9CQm+IdODigTkj1acry7Q7GDJyUmeUZXypOWH m8rXbAtnRo5v7Q+3T190wENU0qwldtWmidbsCqtXXlPmf7Yxg0t//VUtjWVGa08Zz1ncsnvf utuTf+g5GzxY7rs7MXVFtJDAp7nsF1uVpV7IK7EUZyQaajEXFScCAJtDj68rAwAA Cc: Notmuch Mail X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Feb 2012 15:37:04 -0000 Quoth Jesse Rosenthal on Feb 29 at 10:05 am: > On Sun, 26 Feb 2012 16:59:53 -0500, Tom Prince wrote: > > It is probably overkill for any one feature, but it does seem like > > something useful to have. So maybe it would be worthwhile to create > > for this one feature, even it it is overkill. > > I can think of other features where some layer like this would be > useful. It would be great, for example, if it were possible to output > search lines with recipients instead of senders, for the purposes of a > "tag:sent" sort of window. What if the output of search (say, specifically the JSON format) included information on each message in the thread such as the 'message' production from devel/schemata minus the body field? Then the frontend would have loads of information it could produce its own summaries from. (Plus, with a little tweaking, I don't think this would be any more expensive than producing the current notmuch search summary output.)