emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Babel, Python and UTF-8
Date: Thu, 02 Dec 2010 21:10:11 +0100	[thread overview]
Message-ID: <80k4jsszq4.fsf@missioncriticalit.com> (raw)
In-Reply-To: 87hbew7yvi.fsf@gmail.com

Hi Eric,

"Eric Schulte" wrote:
> Sébastien Vauban <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>> Isn't such a prefix already available through the "shebang" option: can't it
>> be multiline?  Anyway, I don't think it's the problem here...
>
> The :shebang header argument is only used for tangling, not during
> evaluation, however if you ever needed to tangle python code blocks with
> non-ASCII encodings this would be the appropriate solution.

Sorry, reading this after the other post...

But, does it still make sense to make that distinction:

- some sort of preamble only for tangling?
- a preamble for evaluation (and tangling)?

Why would the shebang not be inserted as well for evaluation?

Do you/we need:

- one only for eval,
- one only for tangling,
- and one for both?

Depending on that answer, I would maybe make it more explicit what's the role
of each, like:

- :eval-preamble
- :tangle-preambel
- :preamble

But I'm wondering if one sort of preamble wouldn't be enough (and be used both
for tangling and evaluating)?

Best regards,
  Seb

-- 
Sébastien Vauban


_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2010-12-02 20:10 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
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 [this message]
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=80k4jsszq4.fsf@missioncriticalit.com \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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/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).