On Sat, 16 Jul 2011 15:31:31 -0400, Austin Clements <[email protected]> wrote: > I think this could be simplified a lot and many of the known issues > addressed if this were narrowed to *only* resuming from drafts. > message-mode draft files aren't MIME messages (or, at least, they're > never multipart, and message-mode has its own special annotations over > basic RFC 822), so rather than treating the draft as a MIME message > and trying to transform it back into a message-mode-compatible draft > (which, in full generality, would be somewhere between hard and > impossible), what about just dumping the raw contents of the draft > file into a buffer and pointing message-mode at it? If the draft file > is available, you could even open it directly (this wouldn't work for > remote usage, but remote drafts introduce many other problems, too).
I think this is a great idea. Unfortunately, I had a lot of trouble
making message-mode digest an existing buffer. For example, if you take
any existing buffer and call (message-mode) on it, you will notice it
will clear the buffer completely.
I guess I would need to look at how (notmuch-mua-edit-mail) does it but
it was the blocker i had when i tried to figure this out..
Any suggestions?
A.
--
To be naive and easily deceived is impermissible, today more than
ever, when the prevailing untruths may lead to a catastrophe because
they blind people to real dangers and real possibilities.
- Erich Fromm
pgp2pNs2TFrvJ.pgp
Description: PGP signature
_______________________________________________ notmuch mailing list [email protected] http://notmuchmail.org/mailman/listinfo/notmuch
