* mu4e-compose: fix message sending for (near) empty messages

This commit is contained in:
djcb 2012-07-23 00:55:12 +03:00
parent 8e6376ad06
commit b35f9aa9f8
1 changed files with 17 additions and 16 deletions

View File

@ -242,10 +242,10 @@ separator is never written to file. Also see
(goto-char (point-min))
;; search for the first empty line
(if (search-forward-regexp "^$" nil t)
(replace-match sepa)
(replace-match (concat sepa "\n"))
(progn ;; no empty line? then prepend one
(goto-char (point-max))
(insert (concat "\n" sepa)))))))
(insert "\n" sepa "\n"))))))
(defun mu4e~compose-remove-mail-header-separator ()
"Remove `mail-header-separator; we do this before saving a
@ -379,10 +379,11 @@ use the new docid. Returns the full path to the new message."
;; what these 'Sent mail' folders are for!
;;
;; We let message mode take care of this by adding a field
;; Fcc: <full-path-to-message-in-target-folder>
;; in the "message-send-hook" (ie., just before sending).
;; message mode will then take care of the saving when the message is actually
;; sent.
;; in the "message-send-hook" (ie., just before sending). message mode will
;; then take care of the saving when the message is actually sent.
;;
;; note, where and if you make this copy depends on the value of
;; `mu4e-sent-messages-behavior'.