--- /dev/null
+Return-Path: <amdragon@mit.edu>\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 D7335431FBC\r
+ for <notmuch@notmuchmail.org>; Sat, 5 Oct 2013 09:22:15 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.7\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5\r
+ tests=[RCVD_IN_DNSWL_LOW=-0.7] 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 D-WVkyTAV6c6 for <notmuch@notmuchmail.org>;\r
+ Sat, 5 Oct 2013 09:22:09 -0700 (PDT)\r
+Received: from dmz-mailsec-scanner-1.mit.edu (dmz-mailsec-scanner-1.mit.edu\r
+ [18.9.25.12])\r
+ by olra.theworths.org (Postfix) with ESMTP id 69C53431FAF\r
+ for <notmuch@notmuchmail.org>; Sat, 5 Oct 2013 09:22:09 -0700 (PDT)\r
+X-AuditID: 1209190c-b7fd38e0000009aa-5d-52503cb03f03\r
+Received: from mailhub-auth-2.mit.edu ( [18.7.62.36])\r
+ by dmz-mailsec-scanner-1.mit.edu (Symantec Messaging Gateway) with SMTP\r
+ id 17.15.02474.0BC30525; Sat, 5 Oct 2013 12:22:08 -0400 (EDT)\r
+Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11])\r
+ by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id r95GM6BG000374; \r
+ Sat, 5 Oct 2013 12:22:08 -0400\r
+Received: from awakening.csail.mit.edu (awakening.csail.mit.edu [18.26.4.91])\r
+ (authenticated bits=0)\r
+ (User authenticated as amdragon@ATHENA.MIT.EDU)\r
+ by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id r95GM4VX007415\r
+ (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT);\r
+ Sat, 5 Oct 2013 12:22:05 -0400\r
+Received: from amthrax by awakening.csail.mit.edu with local (Exim 4.80)\r
+ (envelope-from <amdragon@mit.edu>)\r
+ id 1VSUcF-0001dB-9B; Sat, 05 Oct 2013 12:22:03 -0400\r
+Date: Sat, 5 Oct 2013 12:22:02 -0400\r
+From: Austin Clements <amdragon@MIT.EDU>\r
+To: Mark Walters <markwalters1009@gmail.com>\r
+Subject: Re: Emacs: how to remove "unread" tag while reading emails\r
+Message-ID: <20131005162202.GJ21611@mit.edu>\r
+References: <87hadi0xse.fsf@boo.workgroup>\r
+ <87pprk3whs.fsf@qmul.ac.uk>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=utf-8\r
+Content-Disposition: inline\r
+Content-Transfer-Encoding: 8bit\r
+In-Reply-To: <87pprk3whs.fsf@qmul.ac.uk>\r
+User-Agent: Mutt/1.5.21 (2010-09-15)\r
+X-Brightmail-Tracker:\r
+ H4sIAAAAAAAAA+NgFlrKKsWRmVeSWpSXmKPExsUixG6norvBJiDI4PxaOYvVc3ksrt+cyWwx\r
+ YdlXdgdmj52z7rJ7LN60n83j2apbzAHMUVw2Kak5mWWpRfp2CVwZZ869Yy9oVa1YuWw/cwPj\r
+ X5kuRk4OCQETictrFjND2GISF+6tZ+ti5OIQEtjHKPFr+TwWCGcDo0TbgWPMEM4pJom3R/cx\r
+ QjhLGCXm7u1iBOlnEVCRONNwlQnEZhPQkNi2fzlYXERAR+L2oQXsIDazgL3E2pufwOLCAs4S\r
+ XbvngNm8QDXLG6aA2UICHhJv77xkgogLSpyc+YQFoldd4s+8S0BXcADZ0hLL/3FAhOUlmrfO\r
+ BnuBE2jt6+3tYLYo0DlTTm5jm8AoPAvJpFlIJs1CmDQLyaQFjCyrGGVTcqt0cxMzc4pTk3WL\r
+ kxPz8lKLdA31cjNL9FJTSjcxgmKDU5JnB+Obg0qHGAU4GJV4eD/u8A8SYk0sK67MPcQoycGk\r
+ JMprAowsIb6k/JTKjMTijPii0pzU4kOMEhzMSiK8Jj+AynlTEiurUovyYVLSHCxK4rw3OeyD\r
+ hATSE0tSs1NTC1KLYLIyHBxKEryHrYGGChalpqdWpGXmlCCkmTg4QYbzAA1/ClLDW1yQmFuc\r
+ mQ6RP8WoKCXOKwRykQBIIqM0D64XlrpeMYoDvSLM+xyknQeY9uC6XwENZgIaHCXhCzK4JBEh\r
+ JdXAKC/3KmZHg8bKZZNLmP7Wu4oG7pQQsEhuPGD9wZPn85RQgQarZ+6/P5d+mjwhL6/gKmv1\r
+ x+2/dn26+nBjTYkjv++xc21SB51VWO7YWPz82VP660frrrqHT9JPR703WVxmlahdkyvDesaz\r
+ Zbep9SPBeXGb6lbXH7z+znKe0L8vFhPtimQSn/19q8RSnJFoqMVcVJwIAJGhhOY4AwAA\r
+Cc: notmuch@notmuchmail.org\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 16:22:16 -0000\r
+\r
+Great list.\r
+\r
+One of the problems with the current approach, which most of these\r
+options share, is that there's no feedback. For example, when I enter\r
+a thread, I have no idea if the first message was unread or not. I'd\r
+like a solution that either naturally doesn't have this problem, that\r
+visually indicates that a message *was* unread, or that delays all\r
+unread marking until you leave the thread (possibly combined with a\r
+visual indication of what will be marked unread). Bonus points if\r
+it's easy to adjust what happens, such as saying "keep everything\r
+unread" or "keep everything unread except this one".\r
+\r
+To this end, here are my two proposals:\r
+\r
+A1) Mark whole thread read when you leave it (via q, X, A or friends)\r
+and provide a binding to leave a thread without marking it read (C-x k\r
+would do, but we should provide an explicit one; perhaps C-u prefixing\r
+other "leave" bindings? For once, C-u is easy to remember because u\r
+is the first letter of unread).\r
+\r
+A2) Like A1, but mark only messages up to and containing point when\r
+you leave a thread.\r
+\r
+In either case, I'd like an echo message when I leave the thread\r
+telling me what happened ("Thread marked as read", "First 3 messages\r
+marked as read; thread archived", etc.). These would blend especially\r
+well with undo, because they would bundle together all read marking\r
+into a single action that would make sense to undo ("Thread marked as\r
+read [C-/ to undo]").\r
+\r
+Both options are highly predictable and easy to understand. They\r
+don't lose information about which messages were unread when you\r
+entered a thread. And they're easy to adjust (you can always -unread\r
+a message manually and then C-u q or whatever to leave without\r
+touching anything else).\r
+\r
+Quoth Mark Walters on Oct 05 at 10:19 am:\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. \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. \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’s the rationale to this behaviour? Am I missing something? \r
+> >\r
+> > Thanks for your attention, gregor\r
projects / notmuch-archives.git / commitdiff