emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Eric Schulte" <schulte.eric@gmail.com>
To: Vincent Beffara <vbeffara@ens-lyon.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: Babel, Python and UTF-8
Date: Wed, 01 Dec 2010 18:18:02 -0700	[thread overview]
Message-ID: <87fwuhas6t.fsf@gmail.com> (raw)
In-Reply-To: <m2d3plm4sx.fsf@ens-lyon.fr> (Vincent Beffara's message of "Thu, 02 Dec 2010 00:50:06 +0100")

Hi Vincent,

I would suggest just trying it out first and seeing if you get an error
without such a line.  Also, you could try adding the line to the
beginning of your code block.

If there is definitely a problem please reply to this thread and we
could easily add a header argument for this case, possibly named
":prefix" which could be used to specify such a code-block-prefix for
code evaluation.  This header argument could then be set globally or on
the file, heading, or code block level.

Best -- Eric

Vincent Beffara <vbeffara@ens-lyon.fr> writes:

> Hi,
>
> I am discovering org-mode and org-babel, and wanted to try it out with
> python code blocks. My use case would involve text processing, encoded
> as UTF-8. Usually a python file has to contain a line to that effect,
> saying sth like   # -*- coding: utf-8 -*-    (without which an error is
> raised).
>
> Is there a way to manage that during org-babel block evaluation ?
>
> Thanks for your help !
>
>        /v
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2010-12-02  1:18 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01 23:50 Babel, Python and UTF-8 Vincent Beffara
2010-12-02  1:18 ` Eric Schulte [this message]
2010-12-02  1:36   ` Vincent Beffara
2010-12-02  9:11     ` Sébastien Vauban
2010-12-02 19:34       ` Eric Schulte
2010-12-02 20:10         ` Sébastien Vauban
2010-12-03 10:27           ` Vincent Beffara
2010-12-03 11:27             ` Sébastien Vauban
2010-12-03 14:30             ` Eric Schulte
2010-12-03 15:43               ` Vincent Beffara
2010-12-05 15:30                 ` Eric Schulte
2010-12-06  9:42                   ` Dan Davison
2010-12-06 11:53                     ` Eric S Fraga
2010-12-06 16:42                     ` Thomas S. Dye
2010-12-06 18:07                       ` Achim Gratz
2010-12-06 18:40                         ` Thomas S. Dye
2010-12-06 18:23                       ` Dan Davison
2010-12-02 14:29     ` Eric Schulte
2010-12-02 16:12       ` Vincent Beffara
2010-12-02 18:23       ` Dan Davison
2010-12-02 19:36         ` Eric Schulte
2010-12-02 20:05           ` Sébastien Vauban
2010-12-02 16:09     ` Sébastien Vauban
2010-12-02 16:44       ` Vincent Beffara
2010-12-03 14:56         ` Christopher Allan Webber

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.orgmode.org/

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

  git send-email \
    --in-reply-to=87fwuhas6t.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=vbeffara@ens-lyon.fr \
    /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/org-mode.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).