unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: 25645@debbugs.gnu.org
Subject: bug#25645: reproducer?
Date: Wed, 04 Oct 2017 12:27:04 +0300	[thread overview]
Message-ID: <83376zz2jb.fsf@gnu.org> (raw)
In-Reply-To: <87o9pnxpuu.fsf@linaro.org> (message from Alex Bennée on Wed, 04 Oct 2017 09:46:17 +0100)

> From: Alex Bennée <alex.bennee@linaro.org>
> Cc: 25645@debbugs.gnu.org
> Date: Wed, 04 Oct 2017 09:46:17 +0100
> 
> > A stab in the dark: what if you filter out message-default-charset
> > from the cloned locals?
> 
> Good guess:
> 
> (defun message-clone-locals (buffer &optional varstr)
>   "Clone the local variables from BUFFER to the current buffer."
>   (message "message-clone-locals: %s" buffer)
>   (let ((locals (with-current-buffer buffer (buffer-local-variables)))
> 	(regexp "^gnus\\|^nn\\|^message\\|^sendmail\\|^smtp\\|^user-mail-address"))
>     (mapcar
>      (lambda (local)
>        (when (and (consp local)
> 		  (car local)
> 		  (string-match regexp (symbol-name (car local)))
> 		  (or (null varstr)
> 		      (string-match varstr (symbol-name (car local)))))
> 	 (ignore-errors
>            (unless (string-match "message-default-charset" (symbol-name (car local)))
>              (message "copying: %s -> %s" (car local) (cdr local))
> 	     (set (make-local-variable (car local))
> 		  (cdr local))))))
>      locals)))
> 
> Although I feel a slightly neater solution is needed.

Hmm... what is non-neat about this one?  The existing filtering
already includes quite a bit of ad-hoc'ery.

> So is the problem we are attempting to double encode an already encoded
> buffer or something else?

Something like that.  I could look deeper, if needed, but frankly the
thick forest of Gnus encoding-related stuff is not something I like to
wander into.  It's easy to break things there because effects are not
localized.

Thanks.





  reply	other threads:[~2017-10-04  9:27 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
2017-10-04  5:51       ` Eli Zaretskii
2017-10-04  8:46         ` Alex Bennée
2017-10-04  9:27           ` Eli Zaretskii [this message]
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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=83376zz2jb.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=25645@debbugs.gnu.org \
    --cc=alex.bennee@linaro.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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).