about summary refs log tree commit diff stats
path: root/worker/types
Commit message (Collapse)AuthorAgeFilesLines
* Remove worker callbacks when Done is receivedDrew DeVault2019-06-022-5/+13
|
* Flesh out multipart switcherDrew DeVault2019-05-201-1/+1
|
* Verify TLS certificatesDrew DeVault2019-05-201-11/+0
| | | | | | I was partway done implementing a UI for users to approve untrusted certs with, but let's just make them configure their servers right instead.
* worker/types/worker: remove mutexSimon Ser2019-05-191-36/+21
| | | | | | | | | | Worker.callbacks contains two types of callbacks: some are action callbacks, some are message callbacks. Each of those is access from one side of the communication channel (UI goroutine vs. worker goroutine). Instead of using a channel, we can use two different maps for each kind. This simplifies the code and also ensures we don't call an action callback instead of a message callback (or the other way around).
* worker/types/worker: make ID allocation atomicSimon Ser2019-05-192-10/+11
| | | | | | | | Message IDs are allocated for both messages from UI to workers and the other way around. Hence, the global nextId variable is accessed from multiple goroutines. Instead, use atomic to access the global counter.
* worker/types/worker: set ID before sending messageSimon Ser2019-05-191-3/+9
| | | | | The previous code set the message ID after sending it, which could result in the receiver reading the ID before it's set.
* s/aerc2/aerc/gDrew DeVault2019-05-171-1/+1
|
* Copy sent emails to the Sent folderDrew DeVault2019-05-152-4/+32
| | | | Or rather, to a user-specified folder
* Implement move, mv commandsDrew DeVault2019-05-141-6/+0
|
* Implement :copy (aka :cp)Drew DeVault2019-05-141-0/+12
|
* worker/types: fix Worker.Callbacks race conditionSimon Ser2019-04-271-15/+41
| | | | | | | | | | | | | Worker.Process* functions were called in different goroutines than Worker.Post*. Protect the map with a mutex. Also make the map unexported to prevent external unprotected accesses. Worker.Process* functions used to delete items from the map. However they didn't delete the element they retrieved: callbacks[msg.InResponseTo()] was read while callbacks[msg] was deleted. I'm not sure I understand why. I tried to delete the element that was accessed - but this broke everything (UI froze at "Connecting..."). I don't believe any elements were actually removed from the map, so the new code just doesn't remove anything.
* Rename FetchMessageBodies to FetchFullMessagesDrew DeVault2019-03-311-2/+2
|
* Don't parse mail in worker; send a reader insteadDrew DeVault2019-03-311-4/+3
|
* Pull BodyStructure up from IMAP workerDrew DeVault2019-03-311-5/+19
|
* Add body fetching support codeDrew DeVault2019-03-291-2/+7
|
* Implement :delete-messageDrew DeVault2019-03-201-0/+10
|
* Implement message store side of message fetchingDrew DeVault2019-03-141-2/+2
|
* Fetch valid UIDs from server after opening dirDrew DeVault2019-03-101-0/+33
|
* Add name to DirectoryInfo messagesDrew DeVault2019-01-131-1/+2
|
* Issue IMAP SELECT commandDrew DeVault2019-01-131-0/+13
|
* Refactoring; consume listing responseDrew DeVault2018-02-011-11/+7
|
* Implement (most of) mailbox listingDrew DeVault2018-02-011-0/+14
|
* Improve loggingDrew DeVault2018-02-011-6/+20
|
* Reduce boilerplate in worker/UIDrew DeVault2018-02-011-0/+59
|
* Add certificate approval flowDrew DeVault2018-01-311-8/+18
|
* Connect to IMAP server, login and idleemersion2018-01-141-0/+2
|
* Move worker into account tabDrew DeVault2018-01-111-1/+1
|
* Initial pass on worker/UI message passingDrew DeVault2018-01-091-0/+55