commit 1d2c4fbb9bdc1078d1727b27139e4df5ba7cb2cb

[Tassilo Horn <tsdh@gnu.org>]

Hi Thierry,

it seems your latest commit broke burying the message buffer after
sending a message for me.  I use

  (setq message-kill-buffer-on-exit t)

and now I get this error after sending messages:

--8<---------------cut here---------------start------------->8---
Debugger entered--Lisp error: (wrong-type-argument stringp nil)
  message-bury()
  message-send-and-exit(nil)
  call-interactively(message-send-and-exit nil nil)
  command-execute(message-send-and-exit)
--8<---------------cut here---------------end--------------->8---

The problem is that `with-current-buffer' doesn't work if the given
buffer is nil?

This simplified definition of `message-bury' works for me:

--8<---------------cut here---------------start------------->8---
(defun message-bury (&optional buffer)
  "Bury this mail BUFFER."
  (when message-return-action
    (apply (car message-return-action) (cdr message-return-action)))
  (bury-buffer buffer))
--8<---------------cut here---------------end--------------->8---

However, I don't use `message-return-action', so I can't tell if
reversing the order (first `message-return-action', then bury the
buffer, instead of the other way round) has any negative effects.

Bye,
Tassilo