Here is a sample that trigger the bug :
"""
import notmuch
db = notmuch.Database()
query = db.create_query("tag:inbox")
for m in query.search_messages():
len(m.get_tags())
"""
---
bindings/python/notmuch/tag.py |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git
Quoth Jameson Graef Rollins on Aug 03 at 2:42 pm:
> On Wed, 3 Aug 2011 16:47:32 -0400, Austin Clements
> wrote:
> > The downside to using document ID's is that we need API's to expose
> > them. My prototype exposes these as opaque "object ID"s, which acts a
> > lot like message IDs, but has no
On Tue, Jul 5, 2011 at 5:42 PM, Austin Clements wrote:
> Quoth Pieter Praet on Jul 05 at ?9:04 pm:
>> On Mon, 04 Jul 2011 20:48:12 +0200, Pieter Praet wrote:
>> > On Mon, 04 Jul 2011 13:56:26 -0400, Austin Clements
>> > wrote:
>> > > I should probably emit two lists per thread: one of matched
Hi,
Two questions:
1) How does notmuch detect the presence of attachments? I have some
messages that have attachments (which I can see and open when reading
the message), but for which the 'attachment' flag is not set (and
therefore don't show up in a search like "from:myfriend AND
On Tue, Jul 5, 2011 at 5:42 PM, Austin Clements amdra...@mit.edu wrote:
Quoth Pieter Praet on Jul 05 at 9:04 pm:
On Mon, 04 Jul 2011 20:48:12 +0200, Pieter Praet pie...@praet.org wrote:
On Mon, 04 Jul 2011 13:56:26 -0400, Austin Clements amdra...@mit.edu
wrote:
I should probably emit
On Wed, 3 Aug 2011 16:47:32 -0400, Austin Clements amdra...@mit.edu wrote:
The patch I posted above includes message ID's in search results as a
proxy for the match set (which can then be used in a tagging operation
to tag exactly the results you saw). However, from an efficiency
standpoint,
Quoth Jameson Graef Rollins on Aug 03 at 2:42 pm:
On Wed, 3 Aug 2011 16:47:32 -0400, Austin Clements amdra...@mit.edu wrote:
The downside to using document ID's is that we need API's to expose
them. My prototype exposes these as opaque object IDs, which acts a
lot like message IDs, but
