unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Austin Clements <amdragon@mit.edu>
To: Jameson Graef Rollins <jrollins@finestructure.net>
Cc: notmuch@notmuchmail.org
Subject: Re: (auto-)tagging sent messages
Date: Mon, 18 Apr 2011 16:26:27 -0400	[thread overview]
Message-ID: <BANLkTimfpvUhEf+UM_0TqwMdMTvzuUjzHw@mail.gmail.com> (raw)
In-Reply-To: <878vv8hh3u.fsf@servo.factory.finestructure.net>

On Sun, Apr 17, 2011 at 2:23 PM, Jameson Graef Rollins
<jrollins@finestructure.net> wrote:
> By giving "notmuch new" a path to a message in the store:
>
>  notmuch new /path/to/message
>
> By feeding "notmuch new" a message on stdin, and then having it write
> the message to a specified location:
>
>  notmuch new /path/to/maildir <message
>
> You could then add the ability to add tags at the time of index:
>
>  notmuch new +foo +bar /path/to/message

I think passing specific messages or directories to notmuch new would
enable some nice features; beyond immediate indexing any tagging of
sent mail, it could be combined with inotify to immediately index any
new mail (something I've been meaning to play with but haven't yet).

However, concurrency and atomicity have to be considered carefully
with any proposal like this.  For example,
  notmuch new +foo +bar /path/to/message
has concurrency hazards: the caller has to store the message before
invoking notmuch new, but if the machine crashes between these two
operations, the message will be indexed with default tags on the next
notmuch new.  Similarly, a chance unrelated invocation of notmuch new
immediately after the message is stored would result in the new
message being indexed with default tags.

  reply	other threads:[~2011-04-18 20:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-14  8:03 (auto-)tagging sent messages Florian Friesdorf
2011-04-16 12:57 ` Pieter Praet
2011-04-16 19:23   ` Tom Prince
2011-04-17 17:53     ` Pieter Praet
2011-04-17 23:17       ` Tom Prince
2011-04-18  6:40         ` Pieter Praet
2011-04-17 18:23   ` Jameson Graef Rollins
2011-04-18 20:26     ` Austin Clements [this message]
2011-04-26  2:38       ` servilio
2011-04-16 22:44 ` Michael Radziej
2011-04-18 13:22   ` Xavier Maillard
2011-04-18 18:44     ` Michael Radziej
2011-04-18 19:29       ` Xavier Maillard
2011-04-19 10:18         ` Michael Radziej
2011-04-20 12:20           ` Xavier Maillard
2011-04-25 20:27             ` Carl Worth
2011-04-25 20:56               ` Tim Gray
2011-04-25 21:41                 ` Carl Worth
2011-04-25 21:59                   ` tracking non-mail files [was: Re: (auto-)tagging sent messages] Jameson Graef Rollins
2011-04-25 22:28                     ` Carl Worth
2011-04-25 22:25               ` (auto-)tagging sent messages Xavier Maillard

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=BANLkTimfpvUhEf+UM_0TqwMdMTvzuUjzHw@mail.gmail.com \
    --to=amdragon@mit.edu \
    --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).