Date: Thu, 11 Mar 2010 17:52:34 -0500 (EST)
From: David A Benjamin <davidben@MIT.EDU>
To: Ben Gamari <bgamari.foss@gmail.com>
In-Reply-To: <4b990b7b.0e67f10a.073c.0686@mx.google.com>
Message-ID: <alpine.DEB.1.10.1003111748020.9755@dr-wily.mit.edu>
References: <4b990b7b.0e67f10a.073c.0686@mx.google.com>
User-Agent: Alpine 1.10 (DEB 962 2008-03-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: notmuch <notmuch@notmuchmail.org>
Subject: Re: [notmuch] Notmuch command interface
Precedence: list

On Thu, 11 Mar 2010, Ben Gamari wrote:
> While the notmuch command-line interface is fantastic, there defintely are a few
> gaps which hurt performance. Since I've been following, I've seen several
> threads on how to handle message addition and initial tagging[1][2]. I recall
> that some time ago Carl had the idea of applying only a 'new' tag during notmuch
> new. I strongly supported this proposal yet it seems that nothing ever became of
> it. Is there a reason for this? Would a patch be accepted?
>

To avoid breaking the current behavior, what if the set of tags applied to 
new/moved/deleted(?) messages could be set on the command line or some 
other library interface, while just perhaps defaulting to unread/inbox? 
This would support both the current behavior and a hooks-like workflow 
without notmuch itself treating any tags (new, unread, inbox, etc.) as 
"special".

David