--- /dev/null
+Return-Path: <dme@dme.org>\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 1F673431FBF\r
+ for <notmuch@notmuchmail.org>; Wed, 7 May 2014 23:14:38 -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 0rYr7oF7fXW3 for <notmuch@notmuchmail.org>;\r
+ Wed, 7 May 2014 23:14:34 -0700 (PDT)\r
+Received: from mail-we0-f175.google.com (mail-we0-f175.google.com\r
+ [74.125.82.175]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+ (No client certificate requested)\r
+ by olra.theworths.org (Postfix) with ESMTPS id 1CBF8431FAE\r
+ for <notmuch@notmuchmail.org>; Wed, 7 May 2014 23:14:33 -0700 (PDT)\r
+Received: by mail-we0-f175.google.com with SMTP id t61so1984775wes.6\r
+ for <notmuch@notmuchmail.org>; Wed, 07 May 2014 23:14:30 -0700 (PDT)\r
+X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\r
+ d=1e100.net; s=20130820;\r
+ h=x-gm-message-state:to:subject:in-reply-to:references:user-agent\r
+ :from:date:message-id:mime-version:content-type;\r
+ bh=MiaOphia8LdyFQizMy5X0RqBXG7JMUB16NNScF1KlXw=;\r
+ b=jUWP+dCDLg/WRLX7tEC6bI7uc8o6twSHBsPvAbv606tpgWf/d1WAy7nS+mDS5DK/hF\r
+ Q3/zRYAMp2j1IFMDP0tSssPOCv9g/LvpCDS0U/9MPk6YscLv/sY2sb8y8PS+AJJtzBRV\r
+ gOa7VOpSk4mZwAkxYVi4Exxkp8JOL2NqAHErzO/bm9p6w94jCHlp0O7G23OSy/h3yRrC\r
+ f+3vvbfACO9acXzdvR1ZZCGFFfTziFFYSfOfeeQmBj0mX43DFg4+Y63IwLWjL72x1p61\r
+ Pu5f1msundDT6tE8JZFuIZ2pQ9+CH76LVIdA+cryCAMqVNVqdPEa9Fbn89mYFZbP+Nj3\r
+ 5IXg==\r
+X-Gm-Message-State:\r
+ ALoCoQlNJ5q5rlJ1Q4Np3FfTZncyOiaVhWRrEHT7w2BTNg2+fqsRq35xc4xEHR03wbqMbjCcbL9Y\r
+X-Received: by 10.194.200.199 with SMTP id ju7mr51041wjc.77.1399529670523;\r
+ Wed, 07 May 2014 23:14:30 -0700 (PDT)\r
+Received: from localhost (disaster-area.hh.sledj.net. [81.149.164.25])\r
+ by mx.google.com with ESMTPSA id pl6sm29895wjc.0.2014.05.07.23.14.28\r
+ for <multiple recipients>\r
+ (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);\r
+ Wed, 07 May 2014 23:14:29 -0700 (PDT)\r
+To: Mark Walters <markwalters1009@gmail.com>, notmuch@notmuchmail.org\r
+Subject: Re: [Patch v3 0/3] emacs: show: redesign unread/read logic\r
+In-Reply-To: <87a9atmpkf.fsf@qmul.ac.uk>\r
+References: <1395777793-13297-1-git-send-email-markwalters1009@gmail.com>\r
+ <cunwqdxfwxn.fsf@hotblack-desiato.hh.sledj.net>\r
+ <87a9atmpkf.fsf@qmul.ac.uk>\r
+User-Agent: Notmuch/0.18 (http://notmuchmail.org) Emacs/24.3.1\r
+ (x86_64-pc-linux-gnu)\r
+From: David Edmondson <dme@dme.org>\r
+Date: Thu, 08 May 2014 07:14:23 +0100\r
+Message-ID: <cunmweser0g.fsf@hotblack-desiato.hh.sledj.net>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/signed; boundary="=-=-=";\r
+ micalg=pgp-sha1; protocol="application/pgp-signature"\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: Thu, 08 May 2014 06:14:38 -0000\r
+\r
+--=-=-=\r
+Content-Type: text/plain\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+On Wed, May 07 2014, Mark Walters wrote:\r
+> A message is marked read if:\r
+>\r
+> 1) if you navigate to a message using n/p (next/prev open message)=20\r
+>\r
+> 2) if you navigate to it using N/P (next/prev message) regardless of\r
+> whether the message is open or closed.\r
+>\r
+> 3) if you go to it using n.s.next-matching-message (not bound by\r
+> default) whether message is open or closed.\r
+>\r
+> 4) when you enter a buffer and notmuch goes to the first open message.\r
+>\r
+> but not marked read in cases like:\r
+>\r
+> 1) opening a message\r
+>\r
+> 2) viewing or entering a message using other notmuch navigation such as\r
+> notmuch-show-advance and friends (bound to space)\r
+\r
+My experience is that this removes the 'unread' tag.\r
+\r
+> 3) viewing or entering a message using arrow keys, page-up page-down,\r
+> ctrl-v mouse clicks etc\r
+>\r
+> Personally, I think marking a closed message read is a bug,\r
+\r
+Agreed.\r
+\r
+> and not marking it read when opening it is too\r
+\r
+Agreed.\r
+\r
+> (at least in many cases).\r
+\r
+I would be happy with just these fixed (i.e. the current behaviour with\r
+those two bug fixes). My typical use is to move around a thread using\r
+Space, Backspace, n, p, N and P with RET, M-RET and C-u M-RET to\r
+manipulate open/closed state (i.e. not the normal emacs movement\r
+commands to move).\r
+\r
+> The other problem with the current approach (in my view) is that if\r
+> you try to use the navigation commands non-interactively then messages\r
+> end up being marked read, even if they are never displayed to the\r
+> user.\r
+\r
+In what cases does this happen? (Not arguing, just not fully\r
+understanding.)\r
+\r
+> Linking into the post-command-hook means that this should "just work".\r
+>\r
+> Questions: What does it mean for a message to be the current message?\r
+> Is it just point being in the message?\r
+\r
+This makes sense to me, other than perhaps "point being in an _open_\r
+message". I don't want moving point through a closed message with C-n to\r
+remove the 'unread' tag.\r
+\r
+> Would you be happy with a message being marked read when point entered\r
+> the message? That could be done from the post-command-hook\r
+> infrastructure to fix some of the problems mentioned above.\r
+>\r
+> I think that is likely that people will disagree on how they want this\r
+> to work so I would like to try and make it customisable so I would\r
+> definitely be interested to see if I can get the behaviour you would\r
+> like from this infrastructure (or something similar).\r
+>\r
+> Best wishes\r
+>\r
+> Mark\r
+\r
+--=-=-=\r
+Content-Type: application/pgp-signature; name="signature.asc"\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v1\r
+\r
+iKYEARECAGYFAlNrIL9fFIAAAAAALgAoaXNzdWVyLWZwckBub3RhdGlvbnMub3Bl\r
+bnBncC5maWZ0aGhvcnNlbWFuLm5ldDc1M0Y5NDJDMEExNjc3MDE4OURGMUYyMDY5\r
+RUNEMEFCRjA0OTY1MTYACgkQaezQq/BJZRY2PQCdHFWkCIz2LtQU3y8G0Vuq0e0G\r
+B44An2FYcBf9P0TMrpkMCdNYEIueSnop\r
+=J8Kd\r
+-----END PGP SIGNATURE-----\r
+--=-=-=--\r