unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Jameson Rollins <jrollins@finestructure.net>
To: Sebastian Spaeth <Sebastian@SSpaeth.de>,
	Notmuch Mail list <notmuch@notmuchmail.org>
Subject: Re: [PATCH] Simplify "unread" tag handling in emacs UI.
Date: Wed, 17 Feb 2010 09:12:35 -0500	[thread overview]
Message-ID: <874olgc5nw.fsf@servo.finestructure.net> (raw)
In-Reply-To: <87ljes0yy0.fsf@SSpaeth.de>

[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]

On Wed, 17 Feb 2010 14:33:11 +0100, "Sebastian Spaeth" <Sebastian@SSpaeth.de> wrote:
> I've been using this for quite some time now and I am pretty happy with
> it. However, there is a problem with this approach as this renders the
> function notmuch-show-next-unread-message useless. 
> 
> This proceeds to the next message, using
> notmuch-show-next-message, which your patch marks automatically as read.
> 
> It then checks the unread status in order to decide whether to proceed
> to the next again. So with your patch notmuch-show-next-unread-message
> will skip through all messages in a thread thinking they are all read
> (and actually marking all as read).

Hey, Sebastian.  I'm glad you've been finding the patch useful.  I'd be
happy to look at improving it, or of course accepting patch.  I was
hoping Carl might process these patch first, in which case it would be
easier to know what any improvements might look like.  I'll send a
separate email to ping Carl about that.

jamie.

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

  reply	other threads:[~2010-02-17 14:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-19 22:54 [PATCH] Simplify "unread" tag handling in emacs UI Jameson Rollins
2010-02-17 13:33 ` Sebastian Spaeth
2010-02-17 14:12   ` Jameson Rollins [this message]
2010-02-24 18:26   ` Carl Worth
2010-02-24 19:20     ` Jameson Rollins
2010-02-25 10:23       ` Sebastian Spaeth
2010-02-26 23:35         ` Carl Worth

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=874olgc5nw.fsf@servo.finestructure.net \
    --to=jrollins@finestructure.net \
    --cc=Sebastian@SSpaeth.de \
    --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).