mu4e: fix byte-compiler warnings

This commit is contained in:
Dirk-Jan C. Binnema 2023-08-10 21:10:58 +03:00
parent e9ce45fde9
commit dd5d5e6bbf
2 changed files with 5 additions and 4 deletions

View File

@ -350,11 +350,12 @@ address is set, use that, otherwise use the From address. Note,
whatever was in the To: field before, goes to the Cc:-list (if
we're doing a reply-to-all). Special case: if we were the sender
of the original, we simple copy the list form the original."
(let ((reply-to
(let* ((reply-to
(append
(plist-get origmsg :to)
(or (plist-get origmsg :reply-to) (plist-get origmsg :from)))))
(cl-delete-duplicates reply-to :test #'mu4e~draft-address-cell-equal)
(or (plist-get origmsg :reply-to) (plist-get origmsg :from))))
(reply-to (cl-delete-duplicates reply-to
:test #'mu4e~draft-address-cell-equal)))
(if mu4e-compose-dont-reply-to-self
(cl-delete-if
(lambda (to-cell)

View File

@ -222,7 +222,7 @@ Checks whether the server process is live."
'(run open listen connect stop)) t))
(defsubst mu4e--server-eat-sexp-from-buf ()
"'Eat' the next s-expression from `mu4e--server-buf'.
"Eat the next s-expression from `mu4e--server-buf'.
Note: this is a string, not an emacs-buffer. `mu4e--server-buf gets
its contents from the mu-servers in the following form:
<`mu4e--server-cookie-pre'><length-in-hex><`mu4e--server-cookie-post'>