Tomi Ollila writes:
>
> The code LGTM. Is there any quoting differences between these 2
> tagging methods ?
>
That's a good point. I added quoting easily enough, but as soon as I
did, I discovered the rest of nmbug has some issues with tags with
spaces in them. I'll see how hard this is to
On Sat, Feb 09 2013, david at tethera.net wrote:
> 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.
>
>
On Sat, Feb 09 2013, da...@tethera.net wrote:
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
Tomi Ollila tomi.oll...@iki.fi writes:
The code LGTM. Is there any quoting differences between these 2
tagging methods ?
That's a good point. I added quoting easily enough, but as soon as I
did, I discovered the rest of nmbug has some issues with tags with
spaces in them. I'll see how hard
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
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