You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Though I'm not really sure what's going on in message-mode, as best I can tell, after sending an e-mail (even with message-kill-buffer-on-exit set), a spare buffer containing my sent mail hangs around, I think due to copying the file out to the FCC directory. Could there be a mu4e option that would enable automatic killing/cleanup of those FCC buffers? (Would it be as simple as calling (kill-buffer) at the end of the message-fcc-handler-function in mu4e~setup-fcc-maybe?)
Thanks!
The text was updated successfully, but these errors were encountered:
Thanks for the report. I could reproduce this; it seems these are draft buffers that hang around. I've added some code to clean them up. Fixed in git. Thanks!
(Note, `message-fcc-handler-function' deals with the messages in the sent-folder).
Ahh, draft buffers. (I thought based on filenames that maybe it had to put the message in a buffer before writing it out to the FCC folder. Drafts makes more sense.)
Though I'm not really sure what's going on in message-mode, as best I can tell, after sending an e-mail (even with
message-kill-buffer-on-exit
set), a spare buffer containing my sent mail hangs around, I think due to copying the file out to the FCC directory. Could there be a mu4e option that would enable automatic killing/cleanup of those FCC buffers? (Would it be as simple as calling(kill-buffer)
at the end of themessage-fcc-handler-function
inmu4e~setup-fcc-maybe
?)Thanks!
The text was updated successfully, but these errors were encountered: