unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Michal Nazarewicz <mina86@mina86.com>
To: Austin Clements <amdragon@MIT.EDU>
Cc: notmuch@notmuchmail.org
Subject: Re: Inheriting tags from parent
Date: Sun, 05 Aug 2012 22:10:14 +0200	[thread overview]
Message-ID: <xa1tmx29t80p.fsf@mina86.com> (raw)
In-Reply-To: <20120803210450.GH22601@mit.edu>

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

> Quoth Michal Nazarewicz on Aug 03 at  4:29 pm:
>> I've just started using notmuch and am wondering if there is a way to
>> make message “inherit” some of the tags from messages they are written
>> in replay to (or in general are part of the same thread).
>> 
>> I'm mostly thinking about a “mute” tag which I'd add to messages that
>> are completely uninteresting to me.  With the “inheritance” mechanism,
>> I'd be able to make notmuch automatically mute all the replays within
>> the same thread.

Austin Clements <amdragon@MIT.EDU> writes:
> I have a hacky and now ancient patch series that you're welcome to try
> porting to a recent notmuch on the inheritable-tags-hack branch at
>   http://awakening.csail.mit.edu/git/notmuch.git
> One general problem with this approach is dealing with threads whose
> messages arrive or are ingested out of order.  I don't think this is
> an insurmountable problem, but my patch certainly doesn't handle it
> correctly.

I'll keep that in mind, but lack of time, won't probably let me play
with it...

> There are also several other solutions to "mute" tags around.  For
> example, some people use a post-new hook to search for threads that
> contain at least one mute tag and then feed these thread IDs back in
> to notmuch tag to add the mute tag to everything in the thread.  I
> believe this is also the approach used by the afew tagging system for
> "killed" threads.

Yeah, that's what I'm doing now.  Basically “notmuch search
--output=threads is:mute” and then join all the lines with “or” to
finally do “notmuch tag +mute <threads>”.  I was, however, hoping for
something more dedicated.

-- 
Best regards,                                         _     _
.o. | Liege of Serenely Enlightened Majesty of      o' \,=./ `o
..o | Computer Science,  Michał “mina86” Nazarewicz    (o o)
ooo +----<email/xmpp: mpn@google.com>--------------ooO--(_)--Ooo--

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

      reply	other threads:[~2012-08-05 20:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-03 14:29 Inheriting tags from parent Michal Nazarewicz
2012-08-03 21:04 ` Austin Clements
2012-08-05 20:10   ` Michal Nazarewicz [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=xa1tmx29t80p.fsf@mina86.com \
    --to=mina86@mina86.com \
    --cc=amdragon@MIT.EDU \
    --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).