Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | notmuch: close tag object | Reto Brunner | 2020-09-24 | 1 | -0/+1 |
| | |||||
* | notmuch: manually close notmuch objects | Reto Brunner | 2020-08-07 | 1 | -0/+3 |
| | | | | | There seems to be some race with the automatic closing that should happen in theory... close it manually where we can to avoid the issue | ||||
* | notmuch: avoid stale DBs | Reto Brunner | 2020-02-16 | 1 | -99/+133 |
| | | | | | | | | | | | | | | Opening a notmuch DB gives you a snapshot of the stage at that specific time. Prior to this, we only reopened the DB upon writing. However, if say a mail sync program like offlineimap is fetching new mail, we would never pick it up. This commit caches a db for a while, so that we don't generate too much overhead and does a reconnect cycle after that. I hardcoded a value as I don't think that having an option would be beneficial. Any write operation (meaning reading mail) anyhow flushes the DB by necessity. (we need to close to commit tag changes, which changing the read state is) | ||||
* | notmuch: emit LabelList event | Reto Brunner | 2019-12-21 | 1 | -0/+17 |
| | |||||
* | notmuch: sync maildir flags | Reto Brunner | 2019-09-16 | 1 | -1/+4 |
| | | | | Syncs back special notmuch tag like unread to the underlying maildir store | ||||
* | notmuch: extract all notmuch db operations. | Reto Brunner | 2019-09-16 | 1 | -0/+179 |
For some reason the current code frequently segfaults due to an invalid C memory address. This commit mediates that by never keeping an object alive longer than absolutely necessary. |