[PATCH] contrib/nmbug: convert to use batch tagging.

2013-02-08 Thread da...@tethera.net
From: David Bremner 

In the case of large changes to the database from git, one of main
current bottlenecks is the large number of execs of notmuch tag. This
avoids that by using use the batch tagging facilities as of notmuch
0.15.

We use "spawn" directly rather than inventing a "notmuch_pipe", since
it seems the only place we need to pipe to notmuch so far.
---

This is only lightly tested; please make sure you have backups of your
database.

I'm not 100% sure about the indentation. No doubt Tomi will let me
know if it can be improved.

 contrib/nmbug/nmbug |   15 ++-
 1 file changed, 10 insertions(+), 5 deletions(-)

diff --git a/contrib/nmbug/nmbug b/contrib/nmbug/nmbug
index f003ef9..c66c526 100755
--- a/contrib/nmbug/nmbug
+++ b/contrib/nmbug/nmbug
@@ -270,17 +270,22 @@ sub do_sync {
 $D_action = '-';
   }

-  foreach my $pair (@{$status->{added}}) {
+  my $notmuch = spawn ({}, '|-', qw/notmuch tag --batch/)
+  or die 'notmuch tag --batch';

-notmuch ('tag', $A_action.$TAGPREFIX.$pair->{tag},
-'id:'.$pair->{id});
+  foreach my $pair (@{$status->{added}}) {
+print $notmuch $A_action.$TAGPREFIX.$pair->{tag}, " -- ",
+  'id:'.$pair->{id};
   }

   foreach my $pair (@{$status->{deleted}}) {
-notmuch ('tag', $D_action.$TAGPREFIX.$pair->{tag},
-'id:'.$pair->{id});
+print $notmuch $D_action.$TAGPREFIX.$pair->{tag},
+  'id:'.$pair->{id};
   }

+  unless (close $notmuch) {
+die "'notmuch tag --batch' exited with nonzero value\n";
+  }
 }


-- 
1.7.10.4



Bug: problem decoding some non-ascii characters in subjects

2013-02-08 Thread Jani Nikula
On Fri, 08 Feb 2013, Albin Stjerna  wrote:
> I've been noticing that notmuch has some problems decoding certain
> strangely-encoded non-ascii characters in certain emails. For example,
> today I got this: [BIBLIST] Digitaliseringensprojektens skadliga
> f=?ISO-8859-1?Q?=F6rk=E4rlek_f=F6r_?= PDF-formatet (should be
> rendered: ?Digitaliseringsprojektens skadliga f?rk?rlek f?r
> PDF-formatet?).
>
> Apparently, some metadata is passed on to help the MUA decode the
> string, but notmuch doesn't seem to handle it. Entire emails can of
> course be supplied as needed.

Please copy paste the Subject: header directly from the message file.


Bug: problem decoding some non-ascii characters in subjects

2013-02-08 Thread Albin Stjerna
Hi,

I've been noticing that notmuch has some problems decoding certain 
strangely-encoded non-ascii characters in certain emails. For example, today I 
got this: [BIBLIST] Digitaliseringensprojektens skadliga 
f=?ISO-8859-1?Q?=F6rk=E4rlek_f=F6r_?= PDF-formatet (should be rendered: 
?Digitaliseringsprojektens skadliga f?rk?rlek f?r PDF-formatet?).

Apparently, some metadata is passed on to help the MUA decode the string, but 
notmuch doesn't seem to handle it. Entire emails can of course be supplied as 
needed.


Bug: problem decoding some non-ascii characters in subjects

2013-02-08 Thread Albin Stjerna
Hi,

I've been noticing that notmuch has some problems decoding certain 
strangely-encoded non-ascii characters in certain emails. For example, today I 
got this: [BIBLIST] Digitaliseringensprojektens skadliga 
f=?ISO-8859-1?Q?=F6rk=E4rlek_f=F6r_?= PDF-formatet (should be rendered: 
»Digitaliseringsprojektens skadliga förkärlek för PDF-formatet«).

Apparently, some metadata is passed on to help the MUA decode the string, but 
notmuch doesn't seem to handle it. Entire emails can of course be supplied as 
needed.
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch


Re: Bug: problem decoding some non-ascii characters in subjects

2013-02-08 Thread Jani Nikula
On Fri, 08 Feb 2013, Albin Stjerna albin.stje...@gmail.com wrote:
 I've been noticing that notmuch has some problems decoding certain
 strangely-encoded non-ascii characters in certain emails. For example,
 today I got this: [BIBLIST] Digitaliseringensprojektens skadliga
 f=?ISO-8859-1?Q?=F6rk=E4rlek_f=F6r_?= PDF-formatet (should be
 rendered: »Digitaliseringsprojektens skadliga förkärlek för
 PDF-formatet«).

 Apparently, some metadata is passed on to help the MUA decode the
 string, but notmuch doesn't seem to handle it. Entire emails can of
 course be supplied as needed.

Please copy paste the Subject: header directly from the message file.
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch


[PATCH] contrib/nmbug: convert to use batch tagging.

2013-02-08 Thread david
From: David Bremner brem...@debian.org

In the case of large changes to the database from git, one of main
current bottlenecks is the large number of execs of notmuch tag. This
avoids that by using use the batch tagging facilities as of notmuch
0.15.

We use spawn directly rather than inventing a notmuch_pipe, since
it seems the only place we need to pipe to notmuch so far.
---

This is only lightly tested; please make sure you have backups of your
database.

I'm not 100% sure about the indentation. No doubt Tomi will let me
know if it can be improved.

 contrib/nmbug/nmbug |   15 ++-
 1 file changed, 10 insertions(+), 5 deletions(-)

diff --git a/contrib/nmbug/nmbug b/contrib/nmbug/nmbug
index f003ef9..c66c526 100755
--- a/contrib/nmbug/nmbug
+++ b/contrib/nmbug/nmbug
@@ -270,17 +270,22 @@ sub do_sync {
 $D_action = '-';
   }
 
-  foreach my $pair (@{$status-{added}}) {
+  my $notmuch = spawn ({}, '|-', qw/notmuch tag --batch/)
+  or die 'notmuch tag --batch';
 
-notmuch ('tag', $A_action.$TAGPREFIX.$pair-{tag},
-'id:'.$pair-{id});
+  foreach my $pair (@{$status-{added}}) {
+print $notmuch $A_action.$TAGPREFIX.$pair-{tag},  -- ,
+  'id:'.$pair-{id};
   }
 
   foreach my $pair (@{$status-{deleted}}) {
-notmuch ('tag', $D_action.$TAGPREFIX.$pair-{tag},
-'id:'.$pair-{id});
+print $notmuch $D_action.$TAGPREFIX.$pair-{tag},
+  'id:'.$pair-{id};
   }
 
+  unless (close $notmuch) {
+die 'notmuch tag --batch' exited with nonzero value\n;
+  }
 }
 
 
-- 
1.7.10.4

___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch


Re: minor fixes for talloc leak logging

2013-02-08 Thread David Bremner
da...@tethera.net writes:

 These are the remaining unapplied patches from 

   id:1358619958-21209-1-git-send-email-da...@tethera.net

 They are rebased to omit the actual command line argument, as suggested by 

  id:87d2wzwmd9@servo.finestructure.net

pushed.

d
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch