1 Return-Path: <m.walters@qmul.ac.uk>
\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 A7046431FAF
\r
6 for <notmuch@notmuchmail.org>; Tue, 21 Feb 2012 00:43:37 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-1.098 tagged_above=-999 required=5
\r
12 tests=[DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001,
\r
13 NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_MED=-2.3] autolearn=disabled
\r
14 Received: from olra.theworths.org ([127.0.0.1])
\r
15 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
16 with ESMTP id DMRZT+L+zyFQ for <notmuch@notmuchmail.org>;
\r
17 Tue, 21 Feb 2012 00:43:33 -0800 (PST)
\r
18 Received: from mail2.qmul.ac.uk (mail2.qmul.ac.uk [138.37.6.6])
\r
19 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
\r
20 (No client certificate requested)
\r
21 by olra.theworths.org (Postfix) with ESMTPS id 8D3EC431FAE
\r
22 for <notmuch@notmuchmail.org>; Tue, 21 Feb 2012 00:43:33 -0800 (PST)
\r
23 Received: from smtp.qmul.ac.uk ([138.37.6.40])
\r
24 by mail2.qmul.ac.uk with esmtp (Exim 4.71)
\r
25 (envelope-from <m.walters@qmul.ac.uk>)
\r
26 id 1RzlJl-0006ck-6x; Tue, 21 Feb 2012 08:43:29 +0000
\r
27 Received: from 94-192-233-223.zone6.bethere.co.uk ([94.192.233.223]
\r
29 by smtp.qmul.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69)
\r
30 (envelope-from <m.walters@qmul.ac.uk>)
\r
31 id 1RzlJl-0004To-0A; Tue, 21 Feb 2012 08:43:25 +0000
\r
32 From: Mark Walters <markwalters1009@gmail.com>
\r
33 To: Michal Sojka <sojkam1@fel.cvut.cz>, Jani Nikula <jani@nikula.org>
\r
34 Subject: Re: [PATCH] emacs: Mention race condition safety in user visible
\r
36 In-Reply-To: <87y5rzmg5v.fsf@steelpick.2x.cz>
\r
37 References: <1329605059-15358-1-git-send-email-sojkam1@fel.cvut.cz>
\r
38 <CAB+hUn907hwS46jM4FY+BAhBTE1VMaMs=q0PFEou3DfWWaDF8g@mail.gmail.com>
\r
39 <87y5rzmg5v.fsf@steelpick.2x.cz>
\r
40 User-Agent: Notmuch/0.11.1+206~g3b67774 (http://notmuchmail.org) Emacs/23.2.1
\r
42 Date: Tue, 21 Feb 2012 08:45:00 +0000
\r
43 Message-ID: <87vcn0tw1f.fsf@qmul.ac.uk>
\r
45 Content-Type: text/plain; charset=us-ascii
\r
46 X-Sender-Host-Address: 94.192.233.223
\r
47 X-QM-SPAM-Info: Sender has good ham record. :)
\r
48 X-QM-Body-MD5: 1bc024877d1328992dec7147d4731c00 (of first 20000 bytes)
\r
49 X-SpamAssassin-Score: -1.8
\r
50 X-SpamAssassin-SpamBar: -
\r
51 X-SpamAssassin-Report: The QM spam filters have analysed this message to
\r
53 spam. We require at least 5.0 points to mark a message as spam.
\r
54 This message scored -1.8 points.
\r
55 Summary of the scoring:
\r
56 * -2.3 RCVD_IN_DNSWL_MED RBL: Sender listed at http://www.dnswl.org/,
\r
58 * [138.37.6.40 listed in list.dnswl.org]
\r
59 * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail
\r
60 provider * (markwalters1009[at]gmail.com)
\r
61 * -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
\r
63 * 0.5 AWL AWL: From: address is in the auto white-list
\r
64 X-QM-Scan-Virus: ClamAV says the message is clean
\r
65 Cc: notmuch@notmuchmail.org
\r
66 X-BeenThere: notmuch@notmuchmail.org
\r
67 X-Mailman-Version: 2.1.13
\r
69 List-Id: "Use and development of the notmuch mail system."
\r
70 <notmuch.notmuchmail.org>
\r
71 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
72 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
73 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
74 List-Post: <mailto:notmuch@notmuchmail.org>
\r
75 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
76 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
77 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
78 X-List-Received-Date: Tue, 21 Feb 2012 08:43:37 -0000
\r
80 On Sun, 19 Feb 2012 08:33:00 +0100, Michal Sojka <sojkam1@fel.cvut.cz> wrote:
\r
81 > On Sun, 19 Feb 2012, Jani Nikula wrote:
\r
82 > > On Feb 19, 2012 12:44 AM, "Michal Sojka" <sojkam1@fel.cvut.cz> wrote:
\r
84 > > > After recent rework of a/A/x/X key bindings, the important paragraph in
\r
85 > > > documentation of `notmuch-show-archive-thread' stayed hidden from users,
\r
86 > > > because no key is bound to this function.
\r
88 > > > This patch copies the important paragraph to the documentation of
\r
89 > > > functions currently bound to keys.
\r
91 > > Hi Michal, this was discussed earlier, and Dmitry convinced me that the
\r
92 > > code does exactly what the user expects it to do (archives only the
\r
93 > > messages in the buffer) so it would be unnecessary and confusing to have
\r
94 > > this documentation. It could be added as a comment for developers I
\r
97 > I'm not sure. As a developer, I'm used to think about race conditions
\r
98 > and the mentioned documentation sounds very racy to me. I guess a lot of
\r
99 > other notmuch users are developers who may think the same.
\r
101 > > > (defun notmuch-show-archive-thread-then-next ()
\r
102 > > > - "Archive each message in thread, then show next thread from search."
\r
104 > What about changing it to "Archive each message in the current buffer, ..."?
\r
106 I like this suggested wording (or perhaps "Archive all messages in the
\r
107 current buffer, ..."). I do not think `Archive each message in thread' is
\r
108 completely clear (is the thread the thread as it is now or as it was
\r
projects / notmuch-archives.git / blob