From: Vincent Beffara <vbeffara@ens-lyon.fr>
To: emacs-orgmode@gnu.org
Subject: Re: Coding systems in Babel
Date: Tue, 07 Dec 2010 14:24:48 +0100 [thread overview]
Message-ID: <m2bp4xaf6n.fsf@ens-lyon.fr> (raw)
In-Reply-To: m2ipz6lt8e.fsf@ens-lyon.fr
Hello,
> So, the instance of python spawned by C-c C-c receives the text as
> latin-1 encoded. Somewhere a conversion from UTF8 to latin-1
> happens. But I don't want that, I want everything to stay in UTF8 from
> the beginning to the end. I guess I have two questions:
>
> At what point in the process is the convertion performed ?
>
> How do I prevent it / how do I specify UTF8 as the exchange format
> between Org-Babel and outside processes spawned by C-c C-c ?
Mmmmkay, answering to myself (you never know, maybe it will be useful to
someone else later ...): the answer to that is in the general
interprocess comunication in Emacs. I ended up doing this:
--8<---------------cut here---------------start------------->8---
(setq default-process-coding-system '(utf-8-unix . utf-8-unix))
--8<---------------cut here---------------end--------------->8---
and everything works fine now.
Having to set this by hand is a bit counter-intuitive though - would it
make sense to have babel set =coding-system-for-read= and
=coding-system-for-write= when running a subprocess ? From what I
understand, =shell-command-on-region= does that automatically but
=org-babel-eval= uses a temporary buffer which loses the encoding choice
for the .org file buffer.
Sorry for the noise, and thanks to all for this excellent tool ! I am
getting addicted to org and babel by the minute ...
Cheers,
/v
next prev parent reply other threads:[~2010-12-07 13:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 17:13 Coding systems in Babel Vincent Beffara
2010-12-07 13:24 ` Vincent Beffara [this message]
2010-12-13 20:00 ` Eric Schulte
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=m2bp4xaf6n.fsf@ens-lyon.fr \
--to=vbeffara@ens-lyon.fr \
--cc=emacs-orgmode@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.