Re: one-time-iterators

2011-05-30 Thread Austin Clements
Quoth Patrick Totzke on May 28 at 9:58 am: > Excerpts from Austin Clements's message of Fri May 27 20:29:24 +0100 2011: > > On Fri, May 27, 2011 at 2:04 PM, Patrick Totzke > > wrote: > > > Excerpts from Austin Clements's message of Fri May 27 03:41:44 +0100 2011: > > >> >> > > Have you tried simp

Re: one-time-iterators

2011-05-28 Thread Patrick Totzke
Excerpts from Austin Clements's message of Fri May 27 20:29:24 +0100 2011: > On Fri, May 27, 2011 at 2:04 PM, Patrick Totzke > wrote: > > Excerpts from Austin Clements's message of Fri May 27 03:41:44 +0100 2011: > >> >> > > Have you tried simply calling list() on your thread > >> >> > > iterator

Re: one-time-iterators

2011-05-27 Thread Austin Clements
On Fri, May 27, 2011 at 2:04 PM, Patrick Totzke wrote: > Excerpts from Austin Clements's message of Fri May 27 03:41:44 +0100 2011: >> >> > > Have you tried simply calling list() on your thread >> >> > > iterator to see how expensive it is?  My bet is that it's quite cheap, >> >> > > both memory-w

Re: one-time-iterators

2011-05-27 Thread Patrick Totzke
Excerpts from Austin Clements's message of Fri May 27 03:41:44 +0100 2011: > >> > > Have you tried simply calling list() on your thread > >> > > iterator to see how expensive it is?  My bet is that it's quite cheap, > >> > > both memory-wise and CPU-wise. > >> > Funny thing: > >> >  q=Database().cr

Re: one-time-iterators

2011-05-26 Thread Austin Clements
On Thu, May 26, 2011 at 6:22 PM, Patrick Totzke wrote: > Excerpts from Austin Clements's message of Thu May 26 22:43:02 +0100 2011: >> > > Though, Patrick, that solution doesn't address your problem.  On the >> > > other hand, it's not clear to me what concurrent access semantics >> > > you're act

Re: one-time-iterators

2011-05-26 Thread Patrick Totzke
Excerpts from Austin Clements's message of Thu May 26 22:43:02 +0100 2011: > http://notmuch.198994.n3.nabble.com/notmuch-s-idea-of-concurrency-failing-an-invocation-tp2373468p2565731.html ah, good old peterson :P thanks. > > > Though, Patrick, that solution doesn't address your problem.  On the >

Re: one-time-iterators

2011-05-26 Thread Patrick Totzke
hehe, did it again (dropping the list from cc). I need to stop using sup :P thanks Austin. Excerpts from Carl Worth's message of Thu May 26 18:20:21 +0100 2011: > On Thu, 26 May 2011 09:31:19 +0100, Patrick Totzke > wrote: > > Wow. This reads really complicated. All I want to say is: > > if I ch

Re: one-time-iterators

2011-05-26 Thread Michael Hudson-Doyle
On Thu, 26 May 2011 10:20:21 -0700, Carl Worth wrote: > On Thu, 26 May 2011 09:31:19 +0100, Patrick Totzke > wrote: > > Wow. This reads really complicated. All I want to say is: > > if I change tags in my search-results view, I get Xapian errors :) > > Yes, that's frustrating. I wish that we ha

Re: one-time-iterators

2011-05-26 Thread Austin Clements
On May 26, 2011 1:20 PM, "Carl Worth" wrote: > > The question: How do you solve this in the emacs code? > > do you store all tids of a query? > > The emacs code does not use the notmuch library interface like your > python bindings do. Instead, it uses the notmuch command-line tool, (and > buffers

Re: one-time-iterators

2011-05-26 Thread Carl Worth
On Thu, 26 May 2011 09:31:19 +0100, Patrick Totzke wrote: > Wow. This reads really complicated. All I want to say is: > if I change tags in my search-results view, I get Xapian errors :) Yes, that's frustrating. I wish that we had a more reliable interface at the notmuch library level. But I'm n