From: Michal Sojka <sojkam1@fel.cvut.cz>
To: Ben Gamari <bgamari.foss@gmail.com>, notmuch <notmuch@notmuchmail.org>
In-Reply-To: <4ba01c54.9298cc0a.66cd.7695@mx.google.com>
References: <4ba01c54.9298cc0a.66cd.7695@mx.google.com>
Date: Thu, 18 Mar 2010 15:02:15 +0100
Message-ID: <87vdct6848.fsf@steelpick.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: Re: [notmuch] Tag search peculiarities
Precedence: list

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