Franz Fellner writes:
>
> On Thu Apr 23 00:21:30 2020, Olly Betts wrote:
>> Then I'd try compacting the database (I think there's a "notmuch
>> compact" subcommand to do this).
> And there we go. Cured the issues. Dropped the very first indexing
> from several minutes to 1.5 seconds on the
Don Zickus writes:
>
> Of course I am using this in a strange context. I am deleting emails
> locally and then running 'notmuch new' to clean up the database.
>
[snip]
> So maybe my use case is unusual and the slowness is expected.
I'd say it's a known performance bug in notmuch that it
On Fri, Apr 24, 2020 at 07:36:23AM -0300, David Bremner wrote:
> Don Zickus writes:
>
> >
> > The only thing I can think of is my fstrim service runs 1x / week on Monday
> > at midnight and maybe that helped clean things up?? Perhaps I should
> > increase that frequency or run it manually when
On Thu Apr 23 00:21:30 2020, Olly Betts wrote:
> First question: what version of Xapian are you using?
On my laptop it's 1.4.15 (arch linux) and the desktop runs 1.4.14 (Gentoo linux)
> And second thing to check, are you committing each message separately?
No, I sync with mbsync which
[Again sorry for double reporting. BTW, where should I search for
previous bugs? I've currently tried the mailing list archive.]
Trying to play with `notmuch` from a wrapper, I've stumbled upon the
following command line flags handling bug:
notmuch show --format json --entire-thread true
Ciprian Dorin Craciun writes:
>
> I've tried to manually edit my `~/.notmuch-config`, and I've seen that
> the field `tags` was written as `tags=unread;inbox;`. In order to
> increase readability I've decided to update my configuration file by
> adding spaces around `=` and `;` as in `tags =
[Sorry if I'm double reporting this. I've tried my best to search for
previous discussions.]
I've tried to manually edit my `~/.notmuch-config`, and I've seen that
the field `tags` was written as `tags=unread;inbox;`. In order to
increase readability I've decided to update my configuration
Don Zickus writes:
>
> The only thing I can think of is my fstrim service runs 1x / week on Monday
> at midnight and maybe that helped clean things up?? Perhaps I should
> increase that frequency or run it manually when things go bad.
>
Is notmuch new still slow on your mail store, or did that
Milton Vandersloot writes:
>
> [PATCH] Let test_emacs_expect_t respect missing external prerequisites
>
> test_emacs_expect_t did not test for missing prerequisites (even though
> it called test_emacs which does it). Fix that by testing for missing
> prerequisites.
>
I agree there's a bug here,
