1 Return-Path: <sojka@os.inf.tu-dresden.de>
\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 8A72D431FB6
\r
6 for <notmuch@notmuchmail.org>; Sat, 18 Feb 2012 23:33:04 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5
\r
12 tests=[RCVD_IN_DNSWL_MED=-2.3] 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 k8yU4d9wewlN for <notmuch@notmuchmail.org>;
\r
16 Sat, 18 Feb 2012 23:33:03 -0800 (PST)
\r
17 Received: from max.feld.cvut.cz (max.feld.cvut.cz [147.32.192.36])
\r
18 by olra.theworths.org (Postfix) with ESMTP id 3B7AD431FAE
\r
19 for <notmuch@notmuchmail.org>; Sat, 18 Feb 2012 23:33:03 -0800 (PST)
\r
20 Received: from localhost (unknown [192.168.200.4])
\r
21 by max.feld.cvut.cz (Postfix) with ESMTP id 89CFB19F35DC;
\r
22 Sun, 19 Feb 2012 08:33:02 +0100 (CET)
\r
23 X-Virus-Scanned: IMAP AMAVIS
\r
24 Received: from max.feld.cvut.cz ([192.168.200.1])
\r
25 by localhost (styx.feld.cvut.cz [192.168.200.4]) (amavisd-new,
\r
27 with ESMTP id 7rxtwFfqs3HM; Sun, 19 Feb 2012 08:33:01 +0100 (CET)
\r
28 Received: from imap.feld.cvut.cz (imap.feld.cvut.cz [147.32.192.34])
\r
29 by max.feld.cvut.cz (Postfix) with ESMTP id A625419F35D3;
\r
30 Sun, 19 Feb 2012 08:33:01 +0100 (CET)
\r
31 Received: from steelpick.2x.cz (unknown [213.29.198.144])
\r
32 (Authenticated sender: sojkam1)
\r
33 by imap.feld.cvut.cz (Postfix) with ESMTPSA id 9318A660968;
\r
34 Sun, 19 Feb 2012 08:33:01 +0100 (CET)
\r
35 Received: from wsh by steelpick.2x.cz with local (Exim 4.77)
\r
36 (envelope-from <sojka@os.inf.tu-dresden.de>)
\r
37 id 1Rz1GW-0005AP-OP; Sun, 19 Feb 2012 08:33:00 +0100
\r
38 From: Michal Sojka <sojkam1@fel.cvut.cz>
\r
39 To: Jani Nikula <jani@nikula.org>
\r
40 Subject: Re: [PATCH] emacs: Mention race condition safety in user visible
\r
43 <CAB+hUn907hwS46jM4FY+BAhBTE1VMaMs=q0PFEou3DfWWaDF8g@mail.gmail.com>
\r
44 References: <1329605059-15358-1-git-send-email-sojkam1@fel.cvut.cz>
\r
45 <CAB+hUn907hwS46jM4FY+BAhBTE1VMaMs=q0PFEou3DfWWaDF8g@mail.gmail.com>
\r
46 User-Agent: Notmuch/0.11.1+210~g5c2fc0a (http://notmuchmail.org) Emacs/23.3.1
\r
47 (x86_64-pc-linux-gnu)
\r
48 Date: Sun, 19 Feb 2012 08:33:00 +0100
\r
49 Message-ID: <87y5rzmg5v.fsf@steelpick.2x.cz>
\r
51 Content-Type: text/plain; charset=us-ascii
\r
52 Cc: notmuch@notmuchmail.org
\r
53 X-BeenThere: notmuch@notmuchmail.org
\r
54 X-Mailman-Version: 2.1.13
\r
56 List-Id: "Use and development of the notmuch mail system."
\r
57 <notmuch.notmuchmail.org>
\r
58 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
59 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
60 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
61 List-Post: <mailto:notmuch@notmuchmail.org>
\r
62 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
63 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
64 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
65 X-List-Received-Date: Sun, 19 Feb 2012 07:33:04 -0000
\r
67 On Sun, 19 Feb 2012, Jani Nikula wrote:
\r
68 > On Feb 19, 2012 12:44 AM, "Michal Sojka" <sojkam1@fel.cvut.cz> wrote:
\r
70 > > After recent rework of a/A/x/X key bindings, the important paragraph in
\r
71 > > documentation of `notmuch-show-archive-thread' stayed hidden from users,
\r
72 > > because no key is bound to this function.
\r
74 > > This patch copies the important paragraph to the documentation of
\r
75 > > functions currently bound to keys.
\r
77 > Hi Michal, this was discussed earlier, and Dmitry convinced me that the
\r
78 > code does exactly what the user expects it to do (archives only the
\r
79 > messages in the buffer) so it would be unnecessary and confusing to have
\r
80 > this documentation. It could be added as a comment for developers I
\r
83 I'm not sure. As a developer, I'm used to think about race conditions
\r
84 and the mentioned documentation sounds very racy to me. I guess a lot of
\r
85 other notmuch users are developers who may think the same.
\r
87 > > (defun notmuch-show-archive-thread-then-next ()
\r
88 > > - "Archive each message in thread, then show next thread from search."
\r
90 What about changing it to "Archive each message in the current buffer, ..."?
\r