From: David Edmondson <dme@dme.org>
To: Mark Walters <markwalters1009@gmail.com>, notmuch@notmuchmail.org
Subject: Re: [Patch v3 0/3] emacs: show: redesign unread/read logic
Date: Wed, 07 May 2014 16:08:52 +0100 [thread overview]
Message-ID: <cunwqdxfwxn.fsf@hotblack-desiato.hh.sledj.net> (raw)
In-Reply-To: <1395777793-13297-1-git-send-email-markwalters1009@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 816 bytes --]
On Tue, Mar 25 2014, Mark Walters wrote:
> The third patch adds my attempt at a plausible logic. I find it works
> very well: it usually does both what I expect and what I want.
Whilst I think that the patch is well done, I don't like the resulting
behaviour. That is a personal preference, of course. At the moment it
doesn't seem that there is a way to accept this patch and (optionally)
retain the existing behaviour. Do you have any thoughts on how we might
achieve that?
I don't have a strong preference for the default behaviour, though I
suspect that something closer to the current behaviour (where a message
is marked seen when it becomes the current message[1]) would better
match user expectation (but this is an opinion, not something founded in
fact).
Footnotes:
[1] Modulo bugs.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 310 bytes --]
next prev parent reply other threads:[~2014-05-07 15:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 20:03 [Patch v3 0/3] emacs: show: redesign unread/read logic Mark Walters
2014-03-25 20:03 ` [Patch v3 1/3] test: make test_emacs call post-command-hook Mark Walters
2014-03-25 20:03 ` [Patch v3 2/3] emacs: show: add an update seen function to post-command-hook Mark Walters
2014-03-25 20:03 ` [Patch v3 3/3] emacs: show: make `seen' mean user viewed whole message Mark Walters
2014-05-07 15:08 ` David Edmondson [this message]
2014-05-07 18:06 ` [Patch v3 0/3] emacs: show: redesign unread/read logic Mark Walters
2014-05-08 6:14 ` David Edmondson
2014-05-08 6:41 ` Mark Walters
2014-05-08 8:09 ` David Edmondson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cunwqdxfwxn.fsf@hotblack-desiato.hh.sledj.net \
--to=dme@dme.org \
--cc=markwalters1009@gmail.com \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).