GNU bug report logs - #25645
26.0.50; message.el: Fcc+handler results in write coding issues in emacs 26

Previous Next

Full log

View this message in rfc822 format

From: Alex Bennée <alex.bennee <at> linaro.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 25645 <at> debbugs.gnu.org
Subject: bug#25645: reproducer?
Date: Wed, 04 Oct 2017 01:31:39 +0100

Eli Zaretskii <eliz <at> gnu.org> writes:

> [Please try to avoid changing the Subject line, as it makes it harder
> for me finding messages relevant to a single discussion.]

Ahh sorry I thought debbugs would munge an appropriate subject when it
received the email.

>
>> From: Alex Bennée <alex.bennee <at> linaro.org>
>> Date: Tue, 03 Oct 2017 15:27:12 +0100
>>
>>
>> Does this count as a reproducer?
>
> It does, but since you have already established that
> message-clone-locals is the culprit, the next question is: what is the
> exact list of local variables that gets cloned here?  Can you post the
> full list?

Sure. From my message log, it seems we clone locals for that buffer at
least twice:

Saving file /home/alex/Maildir/drafts/cur/1507076739.4e7e0c7397b19db2.zen:2,DS...
Wrote /home/alex/Maildir/drafts/cur/1507076739.4e7e0c7397b19db2.zen:2,DS
[mu4e] Saved (10 lines)
Sending...
message-clone-locals: One more run with dump of copy
copying: message-reply-buffer -> nil
copying: message-inserted-headers -> nil
copying: message-send-actions -> nil
copying: message-return-action -> nil
copying: message-exit-actions -> nil
copying: message-kill-actions -> nil
copying: message-postpone-actions -> nil
copying: message-draft-article -> nil
copying: message-reply-headers -> nil
copying: message-newsreader -> nil
copying: message-mailer -> nil
copying: message-post-method -> (nnspool )
copying: message-sent-message-via -> nil
copying: message-checksum -> nil
copying: message-mime-part -> 0
copying: message-signature -> my-sig-function
copying: message-send-mail-real-function -> nil
copying: message-default-charset -> utf-8
copying: message-send-hook -> (#[nil \302=\203	.\303 \210	\203.\304 \210\305\306!\210\307 \210\310 \210~\207 [mu4e-compose-type use-hard-newlines reply mu4e~remove-refs-maybe mu4e-send-harden-newlines set-buffer-modified-p t save-buffer mu4e~compose-setup-fcc-maybe] 2] t)
copying: message-sent-hook -> (#[nil \302.\303\304 	"\207 [mu4e-sent-func mu4e~draft-drafts-folder mu4e-sent-handler mu4e~proc-sent buffer-file-name] 3] t)
Mark set [2 times]
Sending via mail...
Sending email
Sending email done
message-clone-locals: One more run with dump of copy
copying: message-reply-buffer -> nil
copying: message-inserted-headers -> (Message-ID Date)
copying: message-send-actions -> nil
copying: message-return-action -> nil
copying: message-exit-actions -> nil
copying: message-kill-actions -> nil
copying: message-postpone-actions -> nil
copying: message-draft-article -> nil
copying: message-reply-headers -> nil
copying: message-newsreader -> nil
copying: message-mailer -> nil
copying: message-post-method -> (nnspool )
copying: message-sent-message-via -> (mail)
copying: message-checksum -> nil
copying: message-mime-part -> 0
copying: message-signature -> my-sig-function
copying: message-send-mail-real-function -> nil
copying: message-default-charset -> utf-8
copying: message-send-hook -> (#[nil \302=\203	.\303 \210	\203.\304 \210\305\306!\210\307 \210\310 \210~\207 [mu4e-compose-type use-hard-newlines reply mu4e~remove-refs-maybe mu4e-send-harden-newlines set-buffer-modified-p t save-buffer mu4e~compose-setup-fcc-maybe] 2] t)
copying: message-sent-hook -> (#[nil \302.\303\304 	"\207 [mu4e-sent-func mu4e~draft-drafts-folder mu4e-sent-handler mu4e~proc-sent buffer-file-name] 3] t)
Mark set
Saving file /home/alex/Maildir/sent/cur/1507076775.116ee70c083a9def.zen:2,S...


--
Alex Bennée

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.