--- /dev/null
+Return-Path: <m.walters@qmul.ac.uk>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by olra.theworths.org (Postfix) with ESMTP id ED191431FBD\r
+ for <notmuch@notmuchmail.org>; Sat, 5 Oct 2013 02:20:16 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -1.098\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-1.098 tagged_above=-999 required=5\r
+ tests=[DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001,\r
+ NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_MED=-2.3] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+ by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id Zv9BT7C3h++J for <notmuch@notmuchmail.org>;\r
+ Sat, 5 Oct 2013 02:20:09 -0700 (PDT)\r
+Received: from mail2.qmul.ac.uk (mail2.qmul.ac.uk [138.37.6.6])\r
+ (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))\r
+ (No client certificate requested)\r
+ by olra.theworths.org (Postfix) with ESMTPS id 40B9A431FAF\r
+ for <notmuch@notmuchmail.org>; Sat, 5 Oct 2013 02:20:09 -0700 (PDT)\r
+Received: from smtp.qmul.ac.uk ([138.37.6.40])\r
+ by mail2.qmul.ac.uk with esmtp (Exim 4.71)\r
+ (envelope-from <m.walters@qmul.ac.uk>)\r
+ id 1VSO1p-00056f-Dd; Sat, 05 Oct 2013 10:20:03 +0100\r
+Received: from 93-97-24-31.zone5.bethere.co.uk ([93.97.24.31] helo=localhost)\r
+ by smtp.qmul.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.71)\r
+ (envelope-from <m.walters@qmul.ac.uk>)\r
+ id 1VSO1p-0004uR-4o; Sat, 05 Oct 2013 10:20:01 +0100\r
+From: Mark Walters <markwalters1009@gmail.com>\r
+To: Gregor Zattler <telegraph@gmx.net>, notmuch@notmuchmail.org\r
+Subject: Re: Emacs: how to remove "unread" tag while reading emails\r
+In-Reply-To: <87hadi0xse.fsf@boo.workgroup>\r
+References: <87hadi0xse.fsf@boo.workgroup>\r
+User-Agent: Notmuch/0.16 (http://notmuchmail.org) Emacs/23.4.1\r
+ (x86_64-pc-linux-gnu)\r
+Date: Sat, 05 Oct 2013 10:19:59 +0100\r
+Message-ID: <87pprk3whs.fsf@qmul.ac.uk>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=utf-8\r
+Content-Transfer-Encoding: quoted-printable\r
+X-Sender-Host-Address: 93.97.24.31\r
+X-QM-SPAM-Info: Sender has good ham record. :)\r
+X-QM-Body-MD5: 0132fe92fad72818b3ea93df44df63ea (of first 20000 bytes)\r
+X-SpamAssassin-Score: 0.0\r
+X-SpamAssassin-SpamBar: /\r
+X-SpamAssassin-Report: The QM spam filters have analysed this message to\r
+ determine if it is\r
+ spam. We require at least 5.0 points to mark a message as spam.\r
+ This message scored 0.0 points. Summary of the scoring: \r
+ * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail\r
+ provider * (markwalters1009[at]gmail.com)\r
+ * 0.0 AWL AWL: From: address is in the auto white-list\r
+X-QM-Scan-Virus: ClamAV says the message is clean\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Sat, 05 Oct 2013 09:20:17 -0000\r
+\r
+\r
+Hello\r
+\r
+I agree that the unread tag does not work well. There are some instances\r
+which I would class as plain bugs (notmuch-show-next-message which is\r
+bound to N marks the new message read even if it is collapsed) and\r
+other instances where it is not clear what the correct behaviour should\r
+be.\r
+\r
+I have messed around a bit and there seem to be a lot of possible\r
+variants and I don't know whether any would have any consensus.\r
+\r
+One clear divide is whether we should only mark "visited messages" (ie\r
+ones reached using space, n,N,p,P etc in the current bindings) or we\r
+should also make messages seen by scrolling past (eg with page down).\r
+\r
+Anyway here is a list of some possibilities. In all cases I assume we do\r
+not mark any collapsed message read.\r
+\r
+1) Mark a message read when we visit it.\r
+2) Mark a message read when we visit it and the leave it with a "visit\r
+move" (eg n for next message)\r
+\r
+3) Mark a message read if we see the start of the message in the buffer.=20\r
+4) Mark a message read if we have seen the start and end of the message\r
+in the buffer.\r
+5) Mark a message read if we see the end of the message after seeing the\r
+start (rationale moving to the top of the buffer is likely "movement"\r
+rather than "reading")\r
+\r
+6) Something based on how we leave the message: eg page down could mark\r
+all messages which were fully visible read, n (next-open message) could\r
+mark the message being left read.=20\r
+7) Similar to 6) but something where read necessarily includes have seen\r
+the start of the message.\r
+\r
+I think all of these are reasonably easy to implement, and I think I\r
+know which I would like (something like 5 or 7) but it would be\r
+interesting to know if there is any general view or any view on how\r
+customisable this should be.\r
+\r
+Does anyone have any thoughts?\r
+\r
+Best wishes\r
+\r
+Mark\r
+\r
+\r
+\r
+On Wed, 18 Sep 2013, Gregor Zattler <telegraph@gmx.net> wrote:\r
+> Dear notmuchers,\r
+>\r
+> I had difficulties to reliably remove the "unread" tag from\r
+> messages. Mostly I page through threads with the space bar and\r
+> all is well. But when the beginning of the thread is already\r
+> collapsed and I "jump" in the middle of a message pressing space\r
+> bar does not remove the unread tag. It's only removed when\r
+> *entering* the message via space bar from the previous message.\r
+> So the last press on space bar in the previous message jumps to\r
+> the next message and at the same time removes its unread tag.\r
+>\r
+> This seems strange to me. I would say the unread tag should be\r
+> removed when leaving the message with the last press on space\r
+> bar, indicating that one really paged trough the whole message\r
+> instead of only seeing the very beginning of it.\r
+>\r
+> What=E2=80=99s the rationale to this behaviour? Am I missing something?=\r
+=20=20\r
+>\r
+> Thanks for your attention, gregor\r
+> _______________________________________________\r
+> notmuch mailing list\r
+> notmuch@notmuchmail.org\r
+> http://notmuchmail.org/mailman/listinfo/notmuch\r
projects / notmuch-archives.git / commitdiff