Without a reproducer this is essentially not fixable, sorry.
REPORTED RESOLVED INVALID
Aerc is meant to be an interactive client, not a one stop scripting engine.
Not really in favor of such features... we would end up implementing msmtp, offlineimap and the likes if you go down that rabbit hole
We could probably warn if the body would be empty. Though I didn't look at the code (don't know if we only parse upon send, or upon exiting the editor). If we parse upon sending one would need to restructure the code and do the parsing prior to that if you want to be able to see such thing on the confirmation screen
Then you'll need to modify one of the worker messages in a generic way so that we can pass that to the store... probably models.DirectoryInfo? Not sure but that seems to be the most appropriate one ( I think the path sep is per mailbox? Don't know the RFC by hard)
what gave you the notion that this will be implemented client side?
The patches sent by keur do use the workers ability to efficiently get the threads iirc
Do we need to support Pop3 or just imap? Every worker type (imap / maildir /notmuch)
Does aerc already save the headers somewhere? The mail headers? You don't need them. What you need is parts of the imap protocol exchange for imap, for maildir it will be the path separator of the OS (/in all supported OSes) and for notmuch we don't care (:archive doesn't work)
I'd suggest to implement a string Join there with a configurable
seperator which defaults to
/. This wouldn't change anything for all
current users but would make it possible to use with default dovecot configuration.
Should not be configurable but auto detected. The individual workers should be able to tell the delimiter used (for imap it's in the server handshake)
On Wed, Jan 29, 2020 at 09:31:41AM -0000, ~srivathsan wrote:
I would like to take a stab at adding colors to aerc. Has there been any decisions made regarding the possible implementation or configuration?
Please do take this discussion to the normal aerc mailing list. I'm not sure how many of the usual contributors actually browse through the todos. Drew (semi-) jokingly said that he /dev/nulls the todo emails for one...
Is this acceptable for you?