From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: python-shell-send-region uses wrong encoding?
Date: Tue, 29 Oct 2013 19:11:45 +0200 [thread overview]
Message-ID: <83r4b4dmsu.fsf@gnu.org> (raw)
In-Reply-To: <a6279735-24f9-4386-b69f-5390339aa478@default>
> Date: Tue, 29 Oct 2013 09:00:08 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
>
> "you need the encoding system in your buffer which contains
> the source code to be utf-8 to send two bytes for ö. However,
> if it is a single-byte encoding, and given that you select the
> locale that maps the byte F6 to ö, you will get that byte.
>
> PS. Make sure you have -*- coding: utf-8 -*- comment."
I hope you (and everyone else) understand that the above is profoundly
wrong. There's no relation whatsoever between the buffer's file
encoding and the encoding of the material Emacs sends to an inferior
process.
next prev parent reply other threads:[~2013-10-29 17:11 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 [this message]
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
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=83r4b4dmsu.fsf@gnu.org \
--to=eliz@gnu.org \
--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).