From: Jani Nikula <jani@nikula.org>
To: Daniel <quite@hack.org>, notmuch@notmuchmail.org
Subject: Re: synchronizing tag for cur/new location of mail
Date: Tue, 12 Mar 2013 11:24:44 +0100 [thread overview]
Message-ID: <871ubkdifn.fsf@nikula.org> (raw)
In-Reply-To: <khmt34$7k2$1@ger.gmane.org>
On Tue, 12 Mar 2013, Daniel <quite@hack.org> wrote:
> Is there currently no automatic tag that reflects whether a mail was
> found in folder/cur or folder/new? The "unread" tag properly reflects
> the maildir ",S" flag, but the one named "new" doesn't seem to be
> automatic in any way, right?
That's correct, there's no such automatic tag.
The "new" tag is in no way special to notmuch. It's just a typically
used temp tag, usually added by 'notmuch new' based on the user's
new.tags config, and removed by the user's post-new hook.
> I mostly use notmuch as a search backend to mutt, and it certainly is
> very useful. Though since I started feeding rss to maildir, I would like
> the idea of presenting somewhere in my system a list of new and "unseen"
> mails (in the mutt sense, kind of, which you might be familiar with).
From notmuch perspective the difference between "new" and "cur" is just
that the message files in "new" have no maildir flags set, and once
maildir flags are set, they are moved to "cur". No additional semantics
is applied to the file location.
> Presently this seems impossible.
A search for folder:new might be helpful, depending on your setup.
It seems that you may get surprising results if you have more than one
file with the same message-id, and some of those files are in "new" and
some in "cur". (Any code to support automatic "new" tag would have to
handle this too.)
HTH,
Jani.
prev parent reply other threads:[~2013-03-12 10:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 9:38 synchronizing tag for cur/new location of mail Daniel
2013-03-12 10:24 ` Jani Nikula [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=871ubkdifn.fsf@nikula.org \
--to=jani@nikula.org \
--cc=notmuch@notmuchmail.org \
--cc=quite@hack.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).