unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Patrick Totzke <patricktotzke@googlemail.com>
To: Philippe LeCavalier <support@plecavalier.com>,  notmuch@notmuchmail.org
Subject: Re: [alot] mails tagged 'killed' reappearing
Date: Mon, 05 Mar 2012 10:04:21 +0000	[thread overview]
Message-ID: <20120305100421.1665.13686@megatron> (raw)
In-Reply-To: <20120303183732.12306.55008@plc.plecavalier.com>

Hi Phil,

Quoting Philippe LeCavalier (2012-03-03 18:37:32)
>I can't tell if it's _all_ killed mails but I can say for sure that some
>tagged mails reappear in the inbox despite them tagged 'killed' and the
>search mode filter is inbox AND NOT tag:killed.

I presume by reappear you mean that once you receive another mail of that thread,
the thread ends up in your inbox again?

You should be aware that tag "killed" is not special in any kind, nor is "inbox":
They are just strings attached to mails that make it easier for you to filter
your mailboxes.

The feature you might expect: threads tagged "killed" once will never pop up in your inbox
is not a feature of notmuch or alot; it *might* be a feature of your tagging script
if you decide to organize your mails like that.

I can highly recommend Justus' "afew" tagging script https://github.com/teythoon/afew,
which can be configured to provide above mentioned functionality among other things.
For other solutions have a look at http://notmuchmail.org/initial_tagging/.

Best,
/p

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-03 18:37 [alot] mails tagged 'killed' reappearing Philippe LeCavalier
2012-03-05 10:04 ` Patrick Totzke [this message]
     [not found]   ` <20120305130739.12306.39942@plc.plecavalier.com>
2012-03-05 13:58     ` Patrick Totzke
     [not found]   ` <20120306155450.2673.83605@plc.plecavalier.com>
2012-03-06 15:56     ` Patrick Totzke

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=20120305100421.1665.13686@megatron \
    --to=patricktotzke@googlemail.com \
    --cc=notmuch@notmuchmail.org \
    --cc=support@plecavalier.com \
    /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).