2b/110aa2f0bf8f1c3e294c048a6d0359a75ff10c

   1 Return-Path: <amdragon@mit.edu>\r
   2 X-Original-To: notmuch@notmuchmail.org\r
   3 Delivered-To: notmuch@notmuchmail.org\r
   4 Received: from localhost (localhost [127.0.0.1])\r
   5         by olra.theworths.org (Postfix) with ESMTP id 79159431E64\r
   6         for <notmuch@notmuchmail.org>; Wed, 29 Feb 2012 14:47:50 -0800 (PST)\r
   7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
   8 X-Spam-Flag: NO\r
   9 X-Spam-Score: -0.7\r
  10 X-Spam-Level: \r
  11 X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5\r
  12         tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled\r
  13 Received: from olra.theworths.org ([127.0.0.1])\r
  14         by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
  15         with ESMTP id UpBNWezq3emb for <notmuch@notmuchmail.org>;\r
  16         Wed, 29 Feb 2012 14:47:49 -0800 (PST)\r
  17 Received: from dmz-mailsec-scanner-4.mit.edu (DMZ-MAILSEC-SCANNER-4.MIT.EDU\r
  18         [18.9.25.15])\r
  19         by olra.theworths.org (Postfix) with ESMTP id C23E9431FAE\r
  20         for <notmuch@notmuchmail.org>; Wed, 29 Feb 2012 14:47:49 -0800 (PST)\r
  21 X-AuditID: 1209190f-b7f8a6d000000914-a7-4f4eab155beb\r
  22 Received: from mailhub-auth-3.mit.edu ( [18.9.21.43])\r
  23         by dmz-mailsec-scanner-4.mit.edu (Symantec Messaging Gateway) with SMTP\r
  24         id 16.55.02324.51BAE4F4; Wed, 29 Feb 2012 17:47:49 -0500 (EST)\r
  25 Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103])\r
  26         by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id q1TMlmBR031808; \r
  27         Wed, 29 Feb 2012 17:47:48 -0500\r
  28 Received: from awakening.csail.mit.edu (awakening.csail.mit.edu [18.26.4.91])\r
  29         (authenticated bits=0)\r
  30         (User authenticated as amdragon@ATHENA.MIT.EDU)\r
  31         by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id q1TMlkCj016120\r
  32         (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT);\r
  33         Wed, 29 Feb 2012 17:47:47 -0500 (EST)\r
  34 Received: from amthrax by awakening.csail.mit.edu with local (Exim 4.77)\r
  35         (envelope-from <amdragon@mit.edu>)\r
  36         id 1S2sJG-0002qE-FJ; Wed, 29 Feb 2012 17:47:46 -0500\r
  37 From: Austin Clements <amdragon@MIT.EDU>\r
  38 To: Jesse Rosenthal <jrosenthal@jhu.edu>\r
  39 Subject: Re: Replacing my name/email with "me" (or similar) in author lists\r
  40 In-Reply-To: <877gz5tz8p.fsf@jhu.edu>\r
  41 References: <slrnjki3c7.tcm.quite@kelebek.lublin.se>\r
  42         <20120226112210.5422.8471@brick.lan>\r
  43         <87ehthfsyn.fsf@schoepe.localhost> <87fwdxk062.fsf@zancas.localnet>\r
  44         <87ehth8dd2.fsf@hermes.hocat.ca> <878vjl3ck3.fsf@jhu.edu>\r
  45         <20120229153657.GA772@mit.edu> <877gz5tz8p.fsf@jhu.edu>\r
  46 User-Agent: Notmuch/0.11.1+252~gdf1a6d5 (http://notmuchmail.org) Emacs/23.3.1\r
  47         (i486-pc-linux-gnu)\r
  48 Date: Wed, 29 Feb 2012 17:47:46 -0500\r
  49 Message-ID: <87k435ntnx.fsf@awakening.csail.mit.edu>\r
  50 MIME-Version: 1.0\r
  51 Content-Type: text/plain; charset=us-ascii\r
  52 X-Brightmail-Tracker:\r
  53  H4sIAAAAAAAAA+NgFmpgleLIzCtJLcpLzFFi42IR4hTV1hVd7edvcO89n8WN1m5Gi29bdzNa\r
  54         XL85k9ni/t4F7A4sHv++fWf3eLbqFrPHlkPvmT0mPJ7PFMASxWWTkpqTWZZapG+XwJXx/ZRq\r
  55         wTP+ivfrpjE2ML7k6WLk5JAQMJFYvO08M4QtJnHh3nq2LkYuDiGBfYwSv1evZIdwNjBKtC5c\r
  56         xwjhnGSSWPLhPytIi5DAEkaJv4dMQWw2AQ2JbfuXM4LYIkD2grZ17CA2s0CNxK6+s2BxYQFv\r
  57         ie4rS5m6GDk4OAVUJRZdF4CY2c8kcXPBeiaQGlGBRIn1nffBbBagmmWNn1lAbF6gU9/fWMME\r
  58         YQtKnJz5hAVivpbEjX8vmSYwCs5CkpqFJLWAkWkVo2xKbpVubmJmTnFqsm5xcmJeXmqRrole\r
  59         bmaJXmpK6SZGcEBL8u9g/HZQ6RCjAAejEg8vU6GfvxBrYllxZe4hRkkOJiVR3rkrgEJ8Sfkp\r
  60         lRmJxRnxRaU5qcWHGCU4mJVEeD92A+V4UxIrq1KL8mFS0hwsSuK8alrv/IQE0hNLUrNTUwtS\r
  61         i2CyMhwcShK8jquAGgWLUtNTK9Iyc0oQ0kwcnCDDeYCGm4PU8BYXJOYWZ6ZD5E8xKkqJ8waD\r
  62         JARAEhmleXC9sITzilEc6BVhXiuQKh5gsoLrfgU0mAlocACnN8jgkkSElFQDo0Cd3x7h2Jkx\r
  63         d3lu77yy838T/7XTKh0ntTzPBQic+GSZuMD8RmZ3ybaZcQxFihUPLljWOZ+vPxI0Ie+BTODB\r
  64         zgn395gfmdygXCneNuF5/cS/3z6vnatkEnFhMV+KZMeLB4cOJ+zccq6y+nM6154XMk8XhLMt\r
  65         fOy+s3vtxc1fBI591bqk7MCWs1iJpTgj0VCLuag4EQBfqC+XEwMAAA==\r
  66 Cc: Notmuch Mail <notmuch@notmuchmail.org>\r
  67 X-BeenThere: notmuch@notmuchmail.org\r
  68 X-Mailman-Version: 2.1.13\r
  69 Precedence: list\r
  70 List-Id: "Use and development of the notmuch mail system."\r
  71         <notmuch.notmuchmail.org>\r
  72 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
  73         <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
  74 List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
  75 List-Post: <mailto:notmuch@notmuchmail.org>\r
  76 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
  77 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
  78         <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
  79 X-List-Received-Date: Wed, 29 Feb 2012 22:47:50 -0000\r
  80 \r
  81 On Wed, 29 Feb 2012 10:50:46 -0500, Jesse Rosenthal <jrosenthal@jhu.edu> wrote:\r
  82 > On Wed, 29 Feb 2012 10:36:57 -0500, Austin Clements <amdragon@MIT.EDU> wrote:\r
  83 > > What if the output of search (say, specifically the JSON format)\r
  84 > > included information on each message in the thread such as the\r
  85 > > 'message' production from devel/schemata minus the body field?  Then\r
  86 > > the frontend would have loads of information it could produce its own\r
  87 > > summaries from.  (Plus, with a little tweaking, I don't think this\r
  88 > > would be any more expensive than producing the current notmuch search\r
  89 > > summary output.)\r
  90 > \r
  91 > I was hoping for something like that when I started fiddling. But it's\r
  92 > still going to end up being a library question, because\r
  93 > notmuch-search.c, is tied pretty tightly to the lib: i.e. it uses\r
  94 > functions like `notmuch_thread_get_authors (thread)'. I was using the\r
  95 > python bindings, and I ended up having to make a second query off the\r
  96 > thread id (I could have recursed through the messages too, I suppose).\r
  97 > \r
  98 > So I guess what I'm saying is that what you're suggesting sounds great,\r
  99 > but we'd still have to either (a) add new library functions\r
 100 > (`notmuch_thread_get_recipients', `notmuch_thread_abbrev_me'), (b) keep\r
 101 > them all in the client and make pazz and scripters recreate them, or (c)\r
 102 > play around in the sort of client-library space that it sounded like\r
 103 > Bremner was suggesting.\r
 104 \r
 105 I was suggesting just using notmuch_thread_get_toplevel_messages in\r
 106 search (essentially, mixing a bit of show into search).  No library\r
 107 changes necessary.\r
 108 \r
 109 It may still be useful to have a collection of *utilities* that could be\r
 110 reused in bindings; basically, things that currently live in the CLI but\r
 111 could be broken out.  These should live outside of libnotmuch proper.\r
 112 My concern would be what we put in such a library.  Currently, the CLI's\r
 113 internal architecture is quite agile, but as soon as you put some of\r
 114 that in a library, you have a library interface to support.\r