From: Tom Prince <tom.prince@ualberta.net>
To: Pieter Praet <pieter@praet.org>,
Florian Friesdorf <flo@chaoflow.net>,
notmuch@notmuchmail.org
Subject: Re: (auto-)tagging sent messages
Date: Sun, 17 Apr 2011 19:17:40 -0400 [thread overview]
Message-ID: <87k4esjwmj.fsf@hermes.hocat.ca> (raw)
In-Reply-To: <87bp04ix2n.fsf@A7GMS.i-did-not-set--mail-host-address--so-tickle-me>
On 2011-04-17, Pieter Praet wrote:
> On Sat, 16 Apr 2011 15:23:44 -0400, Tom Prince <tom.prince@ualberta.net> wrote:
> > > > Further, for certain mails I sent (like this one ) I would like a
> > > > WAITING tag (or similar) in order to indicate that I am waiting for an
> > > > answer. Currently I set this manually. Could this be achieved through
> > > > some indicators via message mode or similar means? e.g.:
> > > >
> > > > <#notmuch tag=WAITING> analog to <#secure method=pgpmime mode=sign>
> > >
> > > No idea how this works since I don't follow Jameson's crypto branch,
> > > but it's probably not a good idea for this use case since (I presume)
> > > the indicator will become permanently lodged in the content of the
> > > mail, which isn't where highly volatile metadata belongs.
> >
> > I think the idea isn't to save it in the message, but to postprocess the
> > message when sending, remove the marker and add the tag instead.
> >
> > Tom
>
> Seems like a Catch-22 to me.
>
> The marker needs to remain there long enough for Notmuch to index and
> tag the message appropriately (which happens long after message-mode has
> left the building) so it's up to Notmuch itself (as opposed to a
> message-mode hook) to do the pre-/postprocessing.
Not if message mode post-processing is hooked up to something like
notmuch-deliver, that indexes and tags the message on send.
Tom
next prev parent reply other threads:[~2011-04-17 23:17 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 [this message]
2011-04-18 6:40 ` Pieter Praet
2011-04-17 18:23 ` Jameson Graef Rollins
2011-04-18 20:26 ` Austin Clements
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=87k4esjwmj.fsf@hermes.hocat.ca \
--to=tom.prince@ualberta.net \
--cc=flo@chaoflow.net \
--cc=notmuch@notmuchmail.org \
--cc=pieter@praet.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).