From: Michal Sojka <sojkam1@fel.cvut.cz>
To: Ben Gamari <bgamari.foss@gmail.com>, notmuch <notmuch@notmuchmail.org>
Subject: Re: Tag search peculiarities
Date: Thu, 18 Mar 2010 15:02:15 +0100 [thread overview]
Message-ID: <87vdct6848.fsf@steelpick.localdomain> (raw)
In-Reply-To: <4ba01c54.9298cc0a.66cd.7695@mx.google.com>
On Wed, 17 Mar 2010, Ben Gamari wrote:
> While trying perfect my initial tagging script, I have run into a very strange
> set of issue. In my script, I use the following to exclude mailing list traffic
> from my inbox,
>
> notmuch tag -new tag:new and tag:list notmuch tag -new +inbox tag:new
>
> However, I found that mailing list traffic was still getting through.
>
> After investigating further, I found that any query in the form of "tag:inbox
> and tag:$TAG" would return no results. Strangely, all other combinations of tag
> searches (i.e. "tag:lkml and tag:unread") seem to work just fine.
>
> Has anyone else noticed this sort of behavior? Does the inbox tag have some
> special signifigance that I should know of? Is my index just FUBAR? (the ladder
> would be very strange considering it's only a few days old and I can't think of
> any crashes, etc. that might have corrupted it) Any ideas for debugging?
Hi Ben,
I've never had similar problems. AFAIK there is nothing special on inbox
tag. It seems you use your configurable tags patch so I suspected that
patch, but it seems OK.
I'd try the following:
notmuch dump|grep "inbox.*${TAG}"
notmuch dump|grep "${TAG}.*inbox"
It if outputs something, then it's really strange.
-Michal
next prev parent reply other threads:[~2010-03-18 14:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 0:03 Tag search peculiarities Ben Gamari
2010-03-18 14:02 ` Michal Sojka [this message]
2010-03-18 14:27 ` Sandra Snan
2010-03-20 23:09 ` Ben Gamari
2010-03-20 23:22 ` Sandra Snan
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=87vdct6848.fsf@steelpick.localdomain \
--to=sojkam1@fel.cvut.cz \
--cc=bgamari.foss@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).