Hello,
I'm running a pretty innocent notmuch query over a fairly small Maildir:
"((List:debian-devel.lists.debian.org) or ... or
(List:debian-haskell.lists.debian.org) or
(List:debconf-discuss.lists.debian.org)) and (not path:annex/**)"
but gnus-search-run-search fails to return any results. Th
Tomi Ollila writes:
> On Sun, Jul 03 2022, David Bremner wrote:
>
> I've trying to think if there were a way to somehow run only one notmuch
> command instead of notmuch search on all maeby-deleted files -- or
> alternatively attempt to load python bindings and in case of failure use
> the notmuc
On Sun, Jul 03 2022, David Bremner wrote:
> This introduces a dependency on the (new) python bindings, but since
> it also yields a 4x performance improvement on the large performance
> corpus, I think it is worth it.
> ---
> debian/control | 1 +
> notmuch-git.py | 18 +-
>
David Bremner writes:
> This is needed to run (and test) notmuch-git.
applied this one patch to master
___
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-le...@notmuchmail.org
David Bremner writes:
> The original nmbug format (now called version 0) creates 1
> subdirectory of 'tags/' per message. This causes problems for more
> than (roughly) 100k messages.
>
> Version 1 introduces 2 layers of hashed directories. This scheme was
> chose to balance the number of subdire
Tomi Ollila writes:
>> +
>> +
>
> Is three empty lines a bit excessive...?
>
>> +time_done
Fixed in git.
d
___
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-le...@notmuchmail.org
Tomi Ollila writes:
> On Mon, Jul 04 2022, David Bremner wrote:
>
>> Particularly in help messages, nmbug is confusing for users who may
>> have never heard of it.
>
> Good Progress! LGTM!
>
applied to master.
___
notmuch mailing list -- notmuch@notmuc
