From: Jani Nikula <jani@nikula.org>
To: Jameson Graef Rollins <jrollins@finestructure.net>,
Aaron Ecay <aaronecay@gmail.com>,
notmuch@notmuchmail.org
Subject: Re: [PATCH] emacs: call "notmuch tag" only once when archiving a thread
Date: Thu, 05 Jan 2012 22:58:30 +0200 [thread overview]
Message-ID: <87d3axamtl.fsf@nikula.org> (raw)
In-Reply-To: <87vcop3mx1.fsf@servo.finestructure.net>
On Thu, 05 Jan 2012 12:38:18 -0800, Jameson Graef Rollins <jrollins@finestructure.net> wrote:
> On Thu, 05 Jan 2012 22:32:16 +0200, Jani Nikula <jani@nikula.org> wrote:
> > In the search view it does exactly this.
>
> I worry about race conditions in this case, though. I frequently
> archive threads after I've read everything, but I still want to know if
> new message to that thread come in. If I attempt to archive a thread in
> notmuch-search, but a new message has entered the thread without me
> knowing it, I'll archive the new message before I had a chance to look
> at it.
Just to be clear: The patch in question does not alter this
behaviour. The race you describe is there already.
And at a glance, it does not look like something that would be trivial
to fix. The buffer does not have the information to do that.
BR,
Jani.
next prev parent reply other threads:[~2012-01-05 20:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 18:29 [PATCH] emacs: call "notmuch tag" only once when archiving a thread Jani Nikula
2012-01-04 14:13 ` David Edmondson
2012-01-04 14:35 ` Tomi Ollila
2012-01-05 20:10 ` Aaron Ecay
2012-01-05 20:32 ` Jani Nikula
2012-01-05 20:38 ` Jameson Graef Rollins
2012-01-05 20:58 ` Jani Nikula [this message]
2012-01-06 21:31 ` Tomi Ollila
2012-01-09 0:56 ` Aaron Ecay
2012-01-09 1:12 ` Austin Clements
2012-01-09 8:15 ` David Edmondson
2012-01-09 8:41 ` Jani Nikula
2012-01-09 10:38 ` Tomi Ollila
2012-01-09 10:46 ` David Edmondson
2012-01-09 11:31 ` Mark Walters
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=87d3axamtl.fsf@nikula.org \
--to=jani@nikula.org \
--cc=aaronecay@gmail.com \
--cc=jrollins@finestructure.net \
--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).