unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Mark Walters <markwalters1009@gmail.com>
To: notmuch@notmuchmail.org
Subject: Re: [PATCH v2 0/5] emacs: show: redesign unread/read logic
Date: Thu, 19 Dec 2013 19:35:41 +0000	[thread overview]
Message-ID: <87iouktz02.fsf@qmul.ac.uk> (raw)
In-Reply-To: <1387065197-15776-1-git-send-email-markwalters1009@gmail.com>


Hi

I have marked this series as obsolete as I have a cleaner way of doing
some of it. In particular, in my local tree the marking tags
deleted/added is done in such a way that it is easy for show, search and
tree to all use the functionality.

However, any feedback on whether people like the way it behaves is still
very welcome!

(As an aside one reason I like this functionality as well as for unread
handling is it means that changes made in one buffer can be shown in
another automatically without losing information: the original tags
remain clear to the user)

Best wishes

Mark


On Sat, 14 Dec 2013, Mark Walters <markwalters1009@gmail.com> wrote:
> Very impressively I managed to send v1 of this series backwards
> (having read through the patches with --reverse so that log showed
> them in the correct order I forgot to delete the --reverse for the
> send-email)
>
> Anyway this the series in the correct order. v1 (the reversed series) and
> proper cover-letter is at
> id:1387064676-15508-1-git-send-email-markwalters1009@gmail.com
>
> Best wishes
>
> Mark
>
> Mark Walters (5):
>   test: make test_emacs call post-command-hook
>   emacs: tree: make the tree code force the mark read update
>   emacs: show: mark tags changed since buffer loaded
>   emacs: show: add an update seen function to post-command-hook
>   emacs: show: make `seen' mean user viewed whole message
>
>  emacs/notmuch-show.el |  123 +++++++++++++++++++++++++++++++++++++++++--------
>  emacs/notmuch-tag.el  |  105 ++++++++++++++++++++++++++++++------------
>  emacs/notmuch-tree.el |    3 +
>  test/test-lib.el      |   16 ++++++
>  test/test-lib.sh      |    2 +-
>  5 files changed, 198 insertions(+), 51 deletions(-)
>
> -- 
> 1.7.9.1

      parent reply	other threads:[~2013-12-19 19:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-14 23:53 [PATCH v2 0/5] emacs: show: redesign unread/read logic Mark Walters
2013-12-14 23:53 ` [PATCH v2 1/5] test: make test_emacs call post-command-hook Mark Walters
2013-12-14 23:53 ` [PATCH v2 2/5] emacs: tree: make the tree code force the mark read update Mark Walters
2013-12-14 23:53 ` [PATCH v2 3/5] emacs: show: mark tags changed since buffer loaded Mark Walters
2013-12-14 23:53 ` [PATCH v2 4/5] emacs: show: add an update seen function to post-command-hook Mark Walters
2013-12-14 23:53 ` [PATCH v2 5/5] emacs: show: make `seen' mean user viewed whole message Mark Walters
2013-12-19 19:35 ` Mark Walters [this message]

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=87iouktz02.fsf@qmul.ac.uk \
    --to=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).