From: David Froger <david.froger@gmail.com>
To: notmuch@notmuchmail.org
Subject: Re: [announce] Bower 0.4
Date: Tue, 14 Aug 2012 06:59:39 +0200 [thread overview]
Message-ID: <20120814065939.GA31346@david-desktop.localdomain> (raw)
In-Reply-To: <20120812203339.14936.26407@brick.lan>
On Sun, 12 Aug 2012 21:33:39 +0100, Patrick Totzke <patricktotzke@gmail.com> wrote:
> Quoting David Froger (2012-08-12 16:53:43)
> > > > 3. Would it be possible to have the feature 'kill a thread' like Sup have? (see
> > > > http://sup.rubyforge.org/README.txt).
> > >
> > > I haven't needed such a feature so I don't have a clear idea how it
> > > should work. There are some patches/ideas about muting threads using
> > > notmuch generally around here. I guess the simplest thing to do is hide
> > > a thread if it has a certain tag, e.g. "muted" as suggested by notmuch
> > > TODO file, unless you search for it explicitly.
> > I like this solution, I will use it (adding 'and not tag:mutted' at the end of my search).
> > When I'm not interessed with a long discussion on a mailling list, I like to be able to 'kill'
> > the thread so it does not reappear with every new mail.
>
> I'm not sure if this actually solves your problem, because
> notmuch's search is message, not thread based:
> If you search for threads that match "is:inbox and not is:muted", you will see threads
> that contain messages which are tagged with "inbox" and not with "muted".
> This means if you just tag one (or all) msg in a thread "muted" and there is a new response,
> this thread will contain such a matching message again and show up in your result list.
Thanks for the clarification, it's very helpfull!
>
> To make this work, you need to set up your tagging script (that you run after 'notmuch new')
> so that it updates those new messages accordingly. If a msg belongs to a thread that has
> muted messages, also tag the new one muted.
> I can pretty much recommend Justus' tagging script afew: https://github.com/teythoon/afew
> One of the filters that it supports out of the box is exactly the "kill threads" function
> you want.
Thanks, this script looks very cool and I think I will replace mine with it (I should have
visited (http://notmuchmail.org/initial_tagging/ ...). You're right, the filter I'm
interessed is in in aftew/filters/KillThreadsFilter.py, and do this:
for all email M that does not have tag 'killed':
I = thread Id of the email M
if there are emails that have thread id I and the 'killed' tag:
apply 'killed' tag on email E
Thanks again for all the help.
next prev parent reply other threads:[~2012-08-14 4:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-12 5:22 [announce] Bower 0.4 Peter Wang
2012-08-12 12:40 ` David Froger
2012-08-12 14:37 ` Peter Wang
2012-08-12 15:53 ` David Froger
2012-08-12 20:33 ` Patrick Totzke
2012-08-14 4:59 ` David Froger [this message]
2012-08-13 9:10 ` Peter Wang
2012-08-14 5:25 ` David Froger
2012-08-14 12:00 ` Peter Wang
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=20120814065939.GA31346@david-desktop.localdomain \
--to=david.froger@gmail.com \
--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).