unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
To: help-gnu-emacs@gnu.org
Subject: Re: python-shell-send-region uses wrong encoding?
Date: Wed, 30 Oct 2013 07:45:07 +0100	[thread overview]
Message-ID: <5270AAF3.5040906@easy-emacs.de> (raw)
In-Reply-To: <jwvmwlrxx8t.fsf-monnier+gmane.emacs.help@gnu.org>

Am 30.10.2013 04:20, schrieb Stefan Monnier:
>> E.g. the patch below (which causes python-shell-send-string to tell
>> Python that the file sent is using utf-8) should fix your problem (tho
>> it's not a proper fix, since we shouldn't hardcode utf-8 here, but copy
>> which ever -*- coding: -*- coding is in the file).
>
> I installed a variant of that patch in Emacs's trunk, which should fix
> the problem.  The relevant part of the patch is quoted below, so you can
> try it out,
>
>
>          Stefan
>
>
> === modified file 'lisp/progmodes/python.el'
> --- lisp/progmodes/python.el	2013-10-07 18:51:26 +0000
> +++ lisp/progmodes/python.el	2013-10-30 01:28:36 +0000
> @@ -2045,7 +2051,9 @@
>                       (concat (file-remote-p default-directory) "/tmp")
>                     temporary-file-directory))
>                  (temp-file-name (make-temp-file "py"))
> +               (coding-system-for-write 'utf-8)
>                  (file-name (or (buffer-file-name) temp-file-name)))
>             (with-temp-file temp-file-name
> +            (insert "# -*- coding: utf-8 -*-\n")
>               (insert string)
>               (delete-trailing-whitespace))
>
>
>

IIUC the second added line "-*- coding: utf-8 -*-\n" should not be needed, as that's the default at the Python side anyway.

Also functions tracing a possibly error might see a different line-offset that way - just an abstract reasoning so far.



  reply	other threads:[~2013-10-30  6:45 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-29 11:30 python-shell-send-region uses wrong encoding? Ernest Adrogué
2013-10-29 14:24 ` Drew Adams
2013-10-29 14:37   ` Ernest Adrogué
2013-10-29 16:00     ` Drew Adams
2013-10-29 16:54       ` Ernest Adrogué
2013-10-29 17:11       ` Eli Zaretskii
2013-10-29 14:26 ` Andreas Röhler
2013-10-29 14:55   ` Ernest Adrogué
2013-10-29 15:29     ` Andreas Röhler
2013-10-29 15:34     ` Peter Dyballa
2013-10-29 16:34       ` Ernest Adrogué
2013-10-29 17:15         ` Eli Zaretskii
2013-10-29 17:53           ` Ernest Adrogué
2013-10-29 19:10             ` Eli Zaretskii
2013-10-29 20:48               ` Ernest Adrogué
2013-10-29 18:07         ` Peter Dyballa
2013-10-29 20:37           ` Ernest Adrogué
2013-10-29 17:28 ` Stefan Monnier
2013-10-30  3:20   ` Stefan Monnier
2013-10-30  6:45     ` Andreas Röhler [this message]
2013-10-30 11:37       ` Stefan Monnier
2013-10-30 12:08         ` Yuri Khan
2013-10-30 12:45           ` Andreas Röhler
2013-10-31 14:30         ` Ernest Adrogué
2013-10-31 14:31     ` Ernest Adrogué
2013-10-31 17:54     ` Ernest Adrogué
2013-10-31 20:35       ` Stefan Monnier
2013-11-04 19:15       ` Stefan Monnier

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=5270AAF3.5040906@easy-emacs.de \
    --to=andreas.roehler@easy-emacs.de \
    --cc=help-gnu-emacs@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.
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).