On 4/12/2023 1:17 PM, Eric Wong wrote:
> Konstantin Ryabitsev <[email protected]> wrote:
>> On Wed, Apr 12, 2023 at 12:06:53AM +0000, Eric Wong wrote:
>>> I think the reason it's rare in MUAs is that it's potentially
>>> very expensive. But I think the `thread:{subquery}' feature
>>> from notmuch I discussed with Konstantin the other week[1] can
>>> do what you want it to do.
>>>
>>> Keep in mind, notmuch-search-terms(7) states:
>>>
>>> The performance of such queries can vary wildly.
>>>
>>> And that's for a private client tool for a single user.
>>
>> Yes, when I was wondering about that, it was really for the lei side of
>> things. I don't really want to run expensive queries on lore (though I'm okay
>> if we can turn it off for /all/ or other very large lists).
>
> I expect relying on timeouts in an external process will be fine
> for lore, especially since some expensive queries are already
> possible :x
>
> I suppose ITIMER_REAL is better than RLIMIT_CPU since the former
> accounts for I/O time. Xapian makes a lot of small pread
> syscalls so I don't see it being stuck in D-state long on SSDs.
For what is worth to those watching the thread, I was able to get what I
needed via combining [1] with notmuch, and its good enough for my purposes.
Being able to do the thread:{} querying directly on lore would be
convenient, but doing the search locally is good enough for my purposes.
Thanks for the tip on notmuch!
-Jake
[1]: https://github.com/wkz/notmuch-lore
