Hi,
I'm trying to use the notmuch C library in a mail client.
Now, I learned that an open DB is essentially a snapshot at the time of opening.
If I want the current state of the notmuch DB, I need to reopen the DB.
The client I'm running is interactive and can have long running processes.
I'd like
Reto writes:
> I'm trying to use the notmuch C library in a mail client.
> Now, I learned that an open DB is essentially a snapshot at the time of
> opening.
> If I want the current state of the notmuch DB, I need to reopen the DB.
>
> The client I'm running is interactive and can have long runn
Peter Wang writes:
> In particular, timestamps beyond 2038 could overflow the sprinter
> interface on systems where time_t is 64-bit but 'int' is a signed 32-bit
> integer type.
Series pushed to master.
d
___
notmuch mailing list
notmuch@notmuchmail.o
On 13 February 2020 23:54:48 CET, David Bremner wrote:
>Do you have any measurements of time or memory savings?
No, but between not having to do a open/close cycle (including garbage
collection on the go side) and having to do it, I expect it would be better if
the DB can be reopened.
The sugg
