1 Return-Path: <BATV+a0db6f1697bf409106ac+2426+infradead.org+hohndel@bombadil.srs.infradead.org>
\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 7CDEC431FC1
\r
6 for <notmuch@notmuchmail.org>; Thu, 15 Apr 2010 14:07:40 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-1.5 tagged_above=-999 required=5
\r
12 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3] autolearn=unavailable
\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 dCxtKByd-aCk for <notmuch@notmuchmail.org>;
\r
16 Thu, 15 Apr 2010 14:07:38 -0700 (PDT)
\r
17 Received: from bombadil.infradead.org (bombadil.infradead.org [18.85.46.34])
\r
18 by olra.theworths.org (Postfix) with ESMTP id CF5714196F0
\r
19 for <notmuch@notmuchmail.org>; Thu, 15 Apr 2010 14:07:38 -0700 (PDT)
\r
20 Received: from localhost ([::1] helo=x200.gr8dns.org)
\r
21 by bombadil.infradead.org with esmtp (Exim 4.69 #1 (Red Hat Linux))
\r
22 id 1O2WHi-0003K3-A9; Thu, 15 Apr 2010 21:07:38 +0000
\r
23 Received: by x200.gr8dns.org (Postfix, from userid 500)
\r
24 id D9762C005E; Thu, 15 Apr 2010 14:07:37 -0700 (PDT)
\r
25 From: Dirk Hohndel <hohndel@infradead.org>
\r
26 To: Carl Worth <cworth@cworth.org>, notmuch@notmuchmail.org
\r
27 Subject: Re: The archive operation should only archive open messages
\r
28 In-Reply-To: <87633sfnyq.fsf@yoom.home.cworth.org>
\r
29 References: <87633sfnyq.fsf@yoom.home.cworth.org>
\r
30 Date: Thu, 15 Apr 2010 14:07:37 -0700
\r
31 Message-ID: <m3tyrc8lwm.fsf@x200.gr8dns.org>
\r
33 Content-Type: text/plain; charset=us-ascii
\r
34 X-SRS-Rewrite: SMTP reverse-path rewritten from <hohndel@infradead.org> by
\r
35 bombadil.infradead.org See http://www.infradead.org/rpr.html
\r
36 X-BeenThere: notmuch@notmuchmail.org
\r
37 X-Mailman-Version: 2.1.13
\r
39 List-Id: "Use and development of the notmuch mail system."
\r
40 <notmuch.notmuchmail.org>
\r
41 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
42 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
43 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
44 List-Post: <mailto:notmuch@notmuchmail.org>
\r
45 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
46 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
47 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
48 X-List-Received-Date: Thu, 15 Apr 2010 21:07:40 -0000
\r
50 On Thu, 15 Apr 2010 13:41:17 -0700, Carl Worth <cworth@cworth.org> wrote:
\r
51 > One of the searches that I use most frequently, (for mail that I want to
\r
52 > respond to on a fairly timely basis), is
\r
54 > tag:inbox and tag:to-me [*]
\r
56 > Sometimes, this search will show a large mailing-list thread with only a
\r
57 > few messages open. Perhaps part-way through the thread, someone started
\r
58 > to CC me. Or perhaps my address got dropped from the CC at some
\r
59 > point. Either way, I am presented with a subset of the messages from the
\r
60 > thread, even though all of the thread's messages are in my inbox still.
\r
62 > That much is just fine. I'm giving priority to messages where people
\r
63 > thought I would be particularly interested, and that's just as it should
\r
66 > A bad bug occurs when paging through the thread with the space
\r
67 > bar. After showing me these few messages, it will then proceed to
\r
68 > archive *all* the messages in the thread (not only those it showed
\r
69 > me). And I'm likely to be unaware of this since the closed (but not yet
\r
70 > archived) messages are not easily distinguished from messages that were
\r
71 > previously closed and archived.
\r
73 > Some people will claim (and I've even agreed) that the space bar is too
\r
74 > magic. But this bug also happens with an explicit command to archive the
\r
75 > current thread (such as hitting 'a').
\r
77 > I think the fix is to change these commands to only archive the messages
\r
78 > that are currently open. That will make these operations behave as I
\r
79 > expect, and I don't think will cause any unexpected or confusing
\r
80 > behavior. But please let me know if you disagree.
\r
82 I am always confused about the behavior of 'a' - does it archive the
\r
83 current message? Or the current thread? Or the current thread down to
\r
84 where I am? Or (as you propose) just the open messages?
\r
86 I think we really need to spend some time to crsiply define the
\r
87 semantics of these commands.
\r
93 Intel Open Source Technology Center
\r