Dirk-Jan C. Binnema
Dirk-Jan C. Binnema
Well, there are two things I suppose: 1) why does your indexing take so long? After the initial indexing, it should be quite fast (a few seconds) ... do you...
One thing that might help diagnosing further (and assuming `journalctl` here, change as needed): - run a recent 1.9 version (>= 1.9.17 or so should do) - run mu4e with...
Note, I've pushed a bunch of optimizations to `master` which make querying / showing results a _lot_ faster. Of course, this ticket is about _worst_ case performance. Anyway, if this...
I tested with doing a full indexing run (about 1.5 min) and during that time, I can use `mu4e` with queries etc., with hardly noticeable delay.
Overall, `mu` 1.11.x searching is quite a bit faster than 1.10; and I cannot reproduce any of the cases where it suddenly slows down; anyway, there's not much more to...
I just tried with the "Lorem ipsum..." and it works fine. Not sure when this got fixed, but seems to work fine with `master` and only ` mu4e-compose-format-flowed`, not other...
Note, at least mu4e (10.x) has much of the mu4e-alert functionality built-in now. Anyway, such an API is not planned for the foreseeable future, so closing this.
Closing this old issue here, and migrated it to IDEAS.org.
I'm afraid we can't do much about this in mu/mu4e, but I still don't fully understand the problem, but I guess we've spent enough time on it. If this is...
Yes, this is basically what #1454 asks for, so closing this one, one ticket is enough :-)