Re: notmuch-emacs should correctly handle signature status on reply
[notmuch-archives.git] / d6 / 7a958179165a4ff3e4b3f9e1a5fa68d1437b66
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 D4B1A431E82\r
6         for <notmuch@notmuchmail.org>; Sat, 31 Mar 2012 20:23:29 -0700 (PDT)\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 CCtt3O6dNdY9 for <notmuch@notmuchmail.org>;\r
16         Sat, 31 Mar 2012 20:23:29 -0700 (PDT)\r
17 Received: from dmz-mailsec-scanner-5.mit.edu (DMZ-MAILSEC-SCANNER-5.MIT.EDU\r
18         [18.7.68.34])\r
19         by olra.theworths.org (Postfix) with ESMTP id 4BB43431FAF\r
20         for <notmuch@notmuchmail.org>; Sat, 31 Mar 2012 20:23:29 -0700 (PDT)\r
21 X-AuditID: 12074422-b7fd66d0000008f9-27-4f77ca2e907a\r
22 Received: from mailhub-auth-4.mit.edu ( [18.7.62.39])\r
23         by dmz-mailsec-scanner-5.mit.edu (Symantec Messaging Gateway) with SMTP\r
24         id AC.0C.02297.E2AC77F4; Sat, 31 Mar 2012 23:23:26 -0400 (EDT)\r
25 Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103])\r
26         by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id q313NP9U008716; \r
27         Sat, 31 Mar 2012 23:23:25 -0400\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 q313NNNk011529\r
32         (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT);\r
33         Sat, 31 Mar 2012 23:23:24 -0400 (EDT)\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 1SEBNz-0000cq-Dp; Sat, 31 Mar 2012 23:23:23 -0400\r
37 Date: Sat, 31 Mar 2012 23:23:23 -0400\r
38 From: Austin Clements <amdragon@MIT.EDU>\r
39 To: Justus Winter <4winter@informatik.uni-hamburg.de>\r
40 Subject: Re: [RFC] Split notmuch_database_close into two functions\r
41 Message-ID: <20120401032323.GH5949@mit.edu>\r
42 References:\r
43  <1332291311-28954-1-git-send-email-4winter@informatik.uni-hamburg.de>\r
44 MIME-Version: 1.0\r
45 Content-Type: text/plain; charset=us-ascii\r
46 Content-Disposition: inline\r
47 In-Reply-To:\r
48  <1332291311-28954-1-git-send-email-4winter@informatik.uni-hamburg.de>\r
49 User-Agent: Mutt/1.5.21 (2010-09-15)\r
50 X-Brightmail-Tracker:\r
51  H4sIAAAAAAAAA+NgFmphleLIzCtJLcpLzFFi42IRYrdT19U7Ve5vsP6AjMXs1h9MFtdvzmR2\r
52         YPKYeP40m8ezVbeYA5iiuGxSUnMyy1KL9O0SuDKu7XrCWjCPreL5vyksDYzdrF2MnBwSAiYS\r
53         V3ftZYOwxSQu3FsPZHNxCAnsY5Q4+eoJE4SzgVHi2puDUM5JJokVr0+zQDhLGCWmX+4C62cR\r
54         UJVYu/42I4jNJqAhsW3/cjBbRMBUYsODB+wgNrOAtMS3381MILawgJPEmguTwOK8AtoSHe03\r
55         wWwhgUCJnuuP2SDighInZz5hgejVkrjx7yVQLwfYnOX/OEDCnAJBEqtnLQYrERVQkZhychvb\r
56         BEahWUi6ZyHpnoXQvYCReRWjbEpulW5uYmZOcWqybnFyYl5eapGuqV5uZoleakrpJkZwYLso\r
57         7WD8eVDpEKMAB6MSD6/WjHJ/IdbEsuLK3EOMkhxMSqK8044DhfiS8lMqMxKLM+KLSnNSiw8x\r
58         SnAwK4nwdq8u8RfiTUmsrEotyodJSXOwKInzqmu98xMSSE8sSc1OTS1ILYLJynBwKEnw2pwE\r
59         GipYlJqeWpGWmVOCkGbi4AQZzgM03BCkhre4IDG3ODMdIn+KUVFKnNcLJCEAksgozYPrhSWe\r
60         V4ziQK8I85qCVPEAkxZc9yugwUxAg5l5Qa4uLklESEk1MMoKOJrEB5j5H4i+JMf8XCHirpja\r
61         h3mMFw47XX+zo0fd54nJmVgmkYU/TkT/Pu8vLLVrwgnbncoHF50/eelAvEnnm97Ahc9u9M1q\r
62         ltJ3snj58U33XrkStptbHl05V3eC82vI59ovl1Tl9Va8sDq3KKBX85SrbuAqs4I/XbpBb+Se\r
63         GPq3H1vWlK/EUpyRaKjFXFScCAC1keNFFwMAAA==\r
64 Cc: notmuch@notmuchmail.org\r
65 X-BeenThere: notmuch@notmuchmail.org\r
66 X-Mailman-Version: 2.1.13\r
67 Precedence: list\r
68 List-Id: "Use and development of the notmuch mail system."\r
69         <notmuch.notmuchmail.org>\r
70 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
71         <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
72 List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
73 List-Post: <mailto:notmuch@notmuchmail.org>\r
74 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
75 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
76         <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
77 X-List-Received-Date: Sun, 01 Apr 2012 03:23:30 -0000\r
78 \r
79 Quoth Justus Winter on Mar 21 at  1:55 am:\r
80 > I propose to split the function notmuch_database_close into\r
81 > notmuch_database_close and notmuch_database_destroy so that long\r
82 > running processes like alot can close the database while still using\r
83 > data obtained from queries to that database.\r
84 \r
85 Is this actually safe?  My understanding of Xapian::Database::close is\r
86 that, once you've closed the database, basically anything can throw a\r
87 Xapian exception.  A lot of data is retrieved lazily, both by notmuch\r
88 and by Xapian, so simply having, say, a notmuch_message_t object isn't\r
89 enough to guarantee that you'll be able to get data out of it after\r
90 closing the database.  Hence, I don't see how this interface could be\r
91 used correctly.\r
92 \r
93 Maybe you could describe your use case in more detail?\r