Hallo!
On Fri, 28 Jan 2011 15:36:25 +1000, Carl Worth wrote:
> On Thu, 27 Jan 2011 02:17:21 -0700, Thomas Schwinge
> wrote:
> > +# Note that in the way we're setting it above and using it below,
> > +# `additional_headers' will also serve as the header / body separator
> > +# (empty
On Thu, 27 Jan 2011 02:17:21 -0700, Thomas Schwinge
wrote:
> +# Note that in the way we're setting it above and using it below,
> +# `additional_headers' will also serve as the header / body separator
> +# (empty line in between).
Thanks, Thomas.
I've merged this now.
I'd even pref
On Thu, 27 Jan 2011 19:20:00 +0100, Thomas Schwinge
wrote:
> Which is the original idea here? Is it that...
There's no original idea yet. It's essentially an unsolved problem right now.
> * each and every client should catch these kinds of errors, and retry,
> or eventually give up at so
On Thu, 27 Jan 2011 17:20:21 -0500, Austin Clements wrote:
> I'm looking into breaking notmuch new up into small transactions. It
> wouldn't be much a leap from there to simply close and reopen the database
> between transactions if another task wants to use it, which would release
> the lock and
: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20110127/17349725/attachment.pgp>
branches in my head. ]:--8)
>
-- next part --
An HTML attachment was scrubbed...
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20110127/9e7c3dfc/attachment.html>
On Thu, 27 Jan 2011 10:51:42 -0500, Jesse Rosenthal wrote:
> Just a note to say that I finally got around to updating the remote
> usage script on the wiki to what I'm using now. With "--format=raw" in,
> it's all pretty straightforward. The only things the script does now
> are:
Thanks for passi
t
> think anyone has been working on this yet, but if this is a big problem
> for you guys, you might start looking into putting one together.
>
> jamie.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20110127/a987c67d/attachment.html>
tmuch/attachments/20110127/21677515/attachment.pgp>
Looks like eagerly synchronizing tags is easy and works fine, though I need
to beef up the tests and put some transactions around things before I'm
satisfied.
I added a "notmuch_database_remove_message_get" to the public API that's
just like "notmuch_database_remove_message" except that it also re
On Thu, 27 Jan 2011 14:49:43 +1000, Carl Worth wrote:
> On Wed, 26 Jan 2011 12:57:50 -0800, Jameson Rollins
> wrote:
> > The call-process to notmuch in notmuch-query.el was previously sending
> > stderr into the output buffer. This means that if there is any stderr
> > the JSON parsing breaks.
signature
Size: 835 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20110127/eb9e93ae/attachment.pgp>
cation/pgp-signature
Size: 189 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20110127/59847bc2/attachment.pgp>
d.worth at intel.com
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20110127/bb600e96/attachment.pgp>
scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20110127/7cc33d89/attachment.pgp>
I'm looking into breaking notmuch new up into small transactions. It
wouldn't be much a leap from there to simply close and reopen the database
between transactions if another task wants to use it, which would release
the lock and let the queued notmuch task have the database for a bit. It
seems
le
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20110127/f8728db1/attachment-0001.pgp>
On Thu, 27 Jan 2011 13:40:25 -0500, micah anderson wrote:
> Due to my harddisk in my laptop being slow (5400RPM), my notmuch
> database growing, and perhaps some fragmentation somewhere, this has
> become *incredibly* annoying for me. I am checking email every 30
> minutes, and I'm nicing and ioni
;http://notmuchmail.org/pipermail/notmuch/attachments/20110127/10747b55/attachment.pgp>
On Thu, 27 Jan 2011, Thomas Schwinge wrote:
> Signed-off-by: Thomas Schwinge
> ---
> test/test-lib.sh |5 -
> 1 files changed, 4 insertions(+), 1 deletions(-)
>
> diff --git a/test/test-lib.sh b/test/test-lib.sh
> index d179426..f536172 100755
> --- a/test/test-lib.sh
> +++ b/test/test-l
On Thu, 27 Jan 2011, Carl Worth wrote:
> On Wed, 26 Jan 2011 12:57:50 -0800, Jameson Rollins finestructure.net> wrote:
> > The call-process to notmuch in notmuch-query.el was previously sending
> > stderr into the output buffer. This means that if there is any stderr
> > the JSON parsing breaks.
On Thu, 27 Jan 2011, Carl Worth wrote:
> On Thu, 27 Jan 2011 15:03:49 +1000, Carl Worth wrote:
> > Just a few hours ago I attended an interesting talk by Rusty Russell in
> > which he talks about a CCAN module he has written called failtest which
> > provides an implementation of this kind of test
Dear all,
Just a note to say that I finally got around to updating the remote
usage script on the wiki to what I'm using now. With "--format=raw" in,
it's all pretty straightforward. The only things the script does now
are:
1. Produces a slight pause in the "notmuch show" output to avoid that
On Thu, 27 Jan 2011 19:20:00 +0100, Thomas Schwinge
wrote:
> Stepping away from the current code base -- what is notmuch's original
> idea of concurrency? That is, all of us probably know that one:
>
> A Xapian exception occurred opening database: Unable to get write
> lock on /home/t
Hallo!
Stepping away from the current code base -- what is notmuch's original
idea of concurrency? That is, all of us probably know that one:
A Xapian exception occurred opening database: Unable to get write
lock on /home/thomas/Mail-schwinge.name-thomas/.notmuch/xapian:
already
Dear all,
Just a note to say that I finally got around to updating the remote
usage script on the wiki to what I'm using now. With "--format=raw" in,
it's all pretty straightforward. The only things the script does now
are:
1. Produces a slight pause in the "notmuch show" output to avoid that
On Thu, 27 Jan 2011, Thomas Schwinge wrote:
> Signed-off-by: Thomas Schwinge
> ---
> test/test-lib.sh |5 -
> 1 files changed, 4 insertions(+), 1 deletions(-)
>
> diff --git a/test/test-lib.sh b/test/test-lib.sh
> index d179426..f536172 100755
> --- a/test/test-lib.sh
> +++ b/test/test-l
These tests should pass -- but they currently don't.
Signed-off-by: Thomas Schwinge
---
Hallo!
I reported this on IRC some weeks ago; here is a more elaborate report.
What we get from these emails, is an author named ``LWN.net'', and the
``Weekly Notification'' / ``Mailing Lists'' bits are st
On Thu, 27 Jan 2011, Carl Worth wrote:
> On Wed, 26 Jan 2011 12:57:50 -0800, Jameson Rollins
> wrote:
> > The call-process to notmuch in notmuch-query.el was previously sending
> > stderr into the output buffer. This means that if there is any stderr
> > the JSON parsing breaks. Unfortunately c
On Thu, 27 Jan 2011, Carl Worth wrote:
> On Thu, 27 Jan 2011 15:03:49 +1000, Carl Worth wrote:
> > Just a few hours ago I attended an interesting talk by Rusty Russell in
> > which he talks about a CCAN module he has written called failtest which
> > provides an implementation of this kind of test
These tests should pass -- but they currently don't.
Signed-off-by: Thomas Schwinge
---
Hallo!
I reported this on IRC some weeks ago; here is a more elaborate report.
What we get from these emails, is an author named ``LWN.net'', and the
``Weekly Notification'' / ``Mailing Lists'' bits are st
Signed-off-by: Thomas Schwinge
---
test/test-lib.sh |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/test/test-lib.sh b/test/test-lib.sh
index d179426..f536172 100755
--- a/test/test-lib.sh
+++ b/test/test-lib.sh
@@ -351,8 +351,11 @@ ${additional_headers}"
${additiona
Signed-off-by: Thomas Schwinge
---
test/test-lib.sh |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/test/test-lib.sh b/test/test-lib.sh
index d179426..f536172 100755
--- a/test/test-lib.sh
+++ b/test/test-lib.sh
@@ -351,8 +351,11 @@ ${additional_headers}"
${additiona
Sure. I've been wanting to take a crack at notmuch new's atomicity for a while.
Though you'll have to get through some of my outstanding patches. I can only
keep so many branches in my head. ]:--8)
rlb, you expressed an interest in solving this problem, too. Did you make any
headway?
"Carl Wor
34 matches
Mail list logo
