aerc - mirror of ~rjarry's aerc fork - a pretty good email client

	Commit message (Collapse)	Author	Age	Files	Lines
*	notmuch: undefined variable when setting reply flag	Srivathsan Murali	2020-05-26	1	-1/+1
\|
*	Set AnsweredFlag on successful reply	Srivathsan Murali	2020-05-25	2	-0/+60
\|
*	notmuch: remove read handling from FetchMessageBodyPart	Reto Brunner	2020-05-11	1	-13/+0
\|
*	notmuch: emit dirinfo upon label change	Reto Brunner	2020-03-01	1	-0/+3
\|
*	notmuch: align dirInfo logic to the maildir worker	Reto Brunner	2020-02-29	1	-10/+13
\|
*	Add missing notmuch build tags	Jeffas	2020-02-26	2	-0/+4
\|
*	notmuch: refresh dirlist in background	Reto Brunner	2020-02-16	3	-1/+27
\|
*	notmuch: add internal event loop	Reto Brunner	2020-02-16	3	-12/+38
\|
*	notmuch: emit DirInfo upon request	Reto Brunner	2020-02-16	1	-12/+44
\|
*	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)
*	Add labels to index format (%g)	Reto Brunner	2019-12-27	1	-0/+4
\| \| \| \|	Exposes the notmuch tags accordingly, stubs it for the maildir worker.
*	notmuch: emit LabelList event	Reto Brunner	2019-12-21	2	-0/+29
\|
*	Notmuch: be resilient to config errors	Reto Brunner	2019-11-01	1	-3/+22
\| \| \| \| \| \| \| \|	Right now notmuch panics if something goes wrong in the configure event. This patch checks for that and returns an error instead, so that we can at least get the UI up and running (and all the other accounts) The experience will be completely degraded until another configure event occurs.
*	notmuch: ignore comments and blank lines when processing query-map file	Matt Snider	2019-11-01	1	-0/+4
\| \| \| \| \|	A segmentation fault occurs when using the notmuch backend and a `query-map` file that contains blank lines or comments.
*	notmuch: add sort functionality	Reto Brunner	2019-09-20	1	-6/+41
\|
*	notmuch: implement ModifyLabels	Reto Brunner	2019-09-16	1	-26/+61
\|
*	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	3	-175/+250
\| \| \| \| \| \|	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.
*	notmuch: add search / filter capabilities	Reto Brunner	2019-08-29	1	-9/+29
\|
*	Notmuch: use adhoc write connection.	Reto Brunner	2019-08-26	2	-30/+147
\| \| \| \| \| \| \| \|	Notmuch only allows a single write connection, all other clients trying to modify the db block. Hence we should only open one when we actually need it. Apparently we also need to refresh the RO DB connection upon modification, else we get stale message tag results
*	Add notmuch backend	Reto Brunner	2019-08-08	2	-0/+516
	This commit introduces the notmuch backend. The backend is conditionally compiled in if the "notmuch" tag is provided. Most of the message types are implemented, with the notable exceptions of DeleteMessages as well as any copy / move / append type. Reason being, that those aren't normally applicable in a notmuch based workflow. Changes v2 --> v3, based on review comments * Use account config for configuration