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 13:58:40 +0000 [thread overview]
Message-ID: <20120305135840.7429.22093@megatron> (raw)
In-Reply-To: <20120305130739.12306.39942@plc.plecavalier.com>
Quoting Philippe LeCavalier (2012-03-05 13:07:39)
>Quoting Patrick Totzke (2012-03-05 05:04:21)
>>I presume by reappear you mean that once you receive another mail of that thread,
>>the thread ends up in your inbox again?
>Yes.
>>
>>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.
>
>Yeah I know what you mean. But the search mode where the killed threads
>reappear is filtered "inbox AND NOT tag:killed" which is why I do
>presume they shouldn't 'reappear'.
Right, the command that alot fires initially - if not stated otherwise in the config or command line arguments - is
"search tag:inbox AND NOT tag:killed", which opens a new search buffer for query "tag:inbox AND NOT tag:killed".
We might consider changing this, as it indeed suggest that inbox or killed tags are special in some sense.
I'm not sure if its a great idea to not fire any command initially by default. After all,
people don't start up theyr mail client and want to stare at a blank terminal.
Perhaps we could drop the "AND NOT tag:killed" here, I don't really have strong feelings about that.
To change the initial command edit the "initial_command" config option:
http://alot.readthedocs.org/en/latest/configuration/index.html#initial-command
best,
/p
next prev parent reply other threads:[~2012-03-05 13:59 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
[not found] ` <20120305130739.12306.39942@plc.plecavalier.com>
2012-03-05 13:58 ` Patrick Totzke [this message]
[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=20120305135840.7429.22093@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).