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 9F665431FBF
\r
6 for <notmuch@notmuchmail.org>; Wed, 7 May 2014 23:41:32 -0700 (PDT)
\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 469R1dC2k66G for <notmuch@notmuchmail.org>;
\r
17 Wed, 7 May 2014 23:41:27 -0700 (PDT)
\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 A33A7431FAE
\r
22 for <notmuch@notmuchmail.org>; Wed, 7 May 2014 23:41:27 -0700 (PDT)
\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 1WiI1A-0005xf-TE; Thu, 08 May 2014 07:41:23 +0100
\r
27 Received: from 5751dfa2.skybroadband.com ([87.81.223.162] helo=localhost)
\r
28 by smtp.qmul.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.71)
\r
29 (envelope-from <m.walters@qmul.ac.uk>)
\r
30 id 1WiI1A-0001fL-Ic; Thu, 08 May 2014 07:41:20 +0100
\r
31 From: Mark Walters <markwalters1009@gmail.com>
\r
32 To: David Edmondson <dme@dme.org>, notmuch@notmuchmail.org
\r
33 Subject: Re: [Patch v3 0/3] emacs: show: redesign unread/read logic
\r
34 In-Reply-To: <cunmweser0g.fsf@hotblack-desiato.hh.sledj.net>
\r
35 References: <1395777793-13297-1-git-send-email-markwalters1009@gmail.com>
\r
36 <cunwqdxfwxn.fsf@hotblack-desiato.hh.sledj.net>
\r
37 <87a9atmpkf.fsf@qmul.ac.uk>
\r
38 <cunmweser0g.fsf@hotblack-desiato.hh.sledj.net>
\r
39 User-Agent: Notmuch/0.15.2+615~g78e3a93 (http://notmuchmail.org) Emacs/23.4.1
\r
40 (x86_64-pc-linux-gnu)
\r
41 Date: Thu, 08 May 2014 07:41:19 +0100
\r
42 Message-ID: <87iopgkc1c.fsf@qmul.ac.uk>
\r
44 Content-Type: text/plain; charset=us-ascii
\r
45 X-Sender-Host-Address: 87.81.223.162
\r
46 X-QM-Geographic: According to ripencc,
\r
47 this message was delivered by a machine in Britain (UK) (GB).
\r
48 X-QM-SPAM-Info: Sender has good ham record. :)
\r
49 X-QM-Body-MD5: 805c7d5246a0e23729d5cfebc7292ba1 (of first 20000 bytes)
\r
50 X-SpamAssassin-Score: -0.1
\r
51 X-SpamAssassin-SpamBar: /
\r
52 X-SpamAssassin-Report: The QM spam filters have analysed this message to
\r
54 spam. We require at least 5.0 points to mark a message as spam.
\r
55 This message scored -0.1 points.
\r
56 Summary of the scoring:
\r
57 * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail
\r
58 provider * (markwalters1009[at]gmail.com)
\r
59 * -0.1 AWL AWL: From: address is in the auto white-list
\r
60 X-QM-Scan-Virus: ClamAV says the message is clean
\r
61 X-BeenThere: notmuch@notmuchmail.org
\r
62 X-Mailman-Version: 2.1.13
\r
64 List-Id: "Use and development of the notmuch mail system."
\r
65 <notmuch.notmuchmail.org>
\r
66 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
67 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
68 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
69 List-Post: <mailto:notmuch@notmuchmail.org>
\r
70 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
71 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
72 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
73 X-List-Received-Date: Thu, 08 May 2014 06:41:32 -0000
\r
75 On Thu, 08 May 2014, David Edmondson <dme@dme.org> wrote:
\r
76 > On Wed, May 07 2014, Mark Walters wrote:
\r
77 >> A message is marked read if:
\r
79 >> 1) if you navigate to a message using n/p (next/prev open message)
\r
81 >> 2) if you navigate to it using N/P (next/prev message) regardless of
\r
82 >> whether the message is open or closed.
\r
84 >> 3) if you go to it using n.s.next-matching-message (not bound by
\r
85 >> default) whether message is open or closed.
\r
87 >> 4) when you enter a buffer and notmuch goes to the first open message.
\r
89 >> but not marked read in cases like:
\r
91 >> 1) opening a message
\r
93 >> 2) viewing or entering a message using other notmuch navigation such as
\r
94 >> notmuch-show-advance and friends (bound to space)
\r
96 > My experience is that this removes the 'unread' tag.
\r
98 Sorry I was wrong here. This one does mark it read.
\r
100 >> 3) viewing or entering a message using arrow keys, page-up page-down,
\r
101 >> ctrl-v mouse clicks etc
\r
103 This is perhaps a key one: should the above mark it read.
\r
105 >> Personally, I think marking a closed message read is a bug,
\r
109 >> and not marking it read when opening it is too
\r
113 >> (at least in many cases).
\r
115 > I would be happy with just these fixed (i.e. the current behaviour with
\r
116 > those two bug fixes). My typical use is to move around a thread using
\r
117 > Space, Backspace, n, p, N and P with RET, M-RET and C-u M-RET to
\r
118 > manipulate open/closed state (i.e. not the normal emacs movement
\r
119 > commands to move).
\r
121 >> The other problem with the current approach (in my view) is that if
\r
122 >> you try to use the navigation commands non-interactively then messages
\r
123 >> end up being marked read, even if they are never displayed to the
\r
126 > In what cases does this happen? (Not arguing, just not fully
\r
129 I had a series for implementing filtering (ie limiting the open
\r
130 messages) in show where it was the main cause of my stopping. See
\r
131 id:20120429005736.GK2704@mit.edu for details of the problems.
\r
133 >> Linking into the post-command-hook means that this should "just work".
\r
135 >> Questions: What does it mean for a message to be the current message?
\r
136 >> Is it just point being in the message?
\r
138 > This makes sense to me, other than perhaps "point being in an _open_
\r
139 > message". I don't want moving point through a closed message with C-n to
\r
140 > remove the 'unread' tag.
\r
142 Oh yes I completely agree with that.
\r