From: Rob Browning <rlb@defaultvalue.org>
To: Austin Clements <amdragon@MIT.EDU>
Subject: Re: Folder search semantics
References: <1295165458-9573-1-git-send-email-amdragon@mit.edu>
	<20110202050336.GB28537@mit.edu> <87sjw6hx2l.fsf@yoom.home.cworth.org>
	<20110203061429.GD28537@mit.edu>
	<87r5b24h6f.fsf@raven.defaultvalue.org>
Date: Sun, 20 Feb 2011 14:00:48 -0600
In-Reply-To: <87r5b24h6f.fsf@raven.defaultvalue.org> (Rob Browning's message
	of "Sun, 20 Feb 2011 13:52:40 -0600")
Message-ID: <87hbby4gsv.fsf@raven.defaultvalue.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: notmuch@notmuchmail.org
Precedence: list

Rob Browning <rlb@defaultvalue.org> writes:

> And personally, I think I'd prefer that folder: be anchored by default,
> so that folder:work means "the top-level folder named work", but it's
> not a big deal to me as long as there's a fairly easy way to specify
> exactly what I want.

Oh, and in part, the reason why I suspect anchored might be a better
default is that it's more conservative.

For example, someone who mistakenly assumes that folder: is anchored by
default doesn't do any unexpected damage with something like this:

  $ notmuch tag +deleted folder:misc
  $ notmuch search tag:deleted ... | xargs rm

FWIW
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4