all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 25645@debbugs.gnu.org
Subject: bug#25645: reproducer?
Date: Wed, 04 Oct 2017 01:31:39 +0100	[thread overview]
Message-ID: <87r2ujycr8.fsf@linaro.org> (raw)
In-Reply-To: <83efqk1bw4.fsf@gnu.org>


Eli Zaretskii <eliz@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@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 \b\302=\203	.\303 \210	\203.

  reply	other threads:[~2017-10-04  0:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-07 17:00 bug#25645: 26.0.50; message.el: Fcc+handler results in write coding issues in emacs 26 Yuri D'Elia
2017-02-07 17:19 ` Eli Zaretskii
2017-02-07 17:31   ` Yuri D'Elia
2017-09-02 13:40     ` Eli Zaretskii
2017-09-13 18:17       ` Lars Ingebrigtsen
2017-09-22  7:26         ` Alexis
2017-09-22 10:49           ` Yuri D'Elia
2017-09-13 18:16 ` Lars Ingebrigtsen
2017-09-13 20:18   ` Yuri D'Elia
2017-09-13 20:35     ` Lars Ingebrigtsen
2017-09-13 20:43       ` Yuri D'Elia
2017-10-03 14:27 ` bug#25645: reproducer? Alex Bennée
2017-10-03 15:36   ` Eli Zaretskii
2017-10-04  0:31     ` Alex Bennée [this message]
2017-10-04  5:51       ` Eli Zaretskii
2017-10-04  8:46         ` Alex Bennée
2017-10-04  9:27           ` Eli Zaretskii
2017-10-09 13:47           ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r2ujycr8.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=25645@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.