Eric Schulte schulte.e...@gmail.com writes:
Vincent Beffara vbeff...@ens-lyon.fr writes:
Hi,
(and it would be excellent to allow for a code block as a preamble,
instead of a string in the header or as an alternative, because
preambles once they are allowed tend to grow uncontrollably ;-)
Dan Davison dandavis...@gmail.com writes:
This makes me think of another good use of the sbe (src block eval)
function. I'm often seeing Org documents with a src block like this,
#+source: essential-document-config
#+begin_src emacs-lisp
;; some essential document-specific configuration
Hi Dan,
Emacs configuration is one of the highest barriers to entry for
potential adopters of Org-mode, IMO. The idea of context-sensitive
configuration is potentially terrific. It gets the user to work more
quickly than would otherwise be the case. The problem I've run into
is that
Thomas S. Dye t...@tsdye.com writes:
Emacs configuration is one of the highest barriers to entry for
potential adopters of Org-mode, IMO. The idea of context-sensitive
configuration is potentially terrific. It gets the user to work more
quickly than would otherwise be the case. The problem
Thomas S. Dye t...@tsdye.com writes:
Hi Dan,
Emacs configuration is one of the highest barriers to entry for
potential adopters of Org-mode, IMO. The idea of context-sensitive
configuration is potentially terrific. It gets the user to work more
quickly than would otherwise be the case.
On Dec 6, 2010, at 8:07 AM, Achim Gratz wrote:
Thomas S. Dye t...@tsdye.com writes:
Emacs configuration is one of the highest barriers to entry for
potential adopters of Org-mode, IMO. The idea of context-sensitive
configuration is potentially terrific. It gets the user to work more
quickly
Vincent Beffara vbeff...@ens-lyon.fr writes:
Hi,
(and it would be excellent to allow for a code block as a preamble,
instead of a string in the header or as an alternative, because
preambles once they are allowed tend to grow uncontrollably ;-)
This is currently possible using the `sbe'
Hi,
preamble sounds fine (and it would be excellent to allow for a code
block as a preamble, instead of a string in the header or as an
alternative, because preambles once they are allowed tend to grow
uncontrollably ;-)
The :shebang header argument is only used for tangling, not during
Hi Vincent,
Vincent Beffara wrote:
preamble sounds fine (and it would be excellent to allow for a code
block as a preamble, instead of a string in the header or as an
alternative, because preambles once they are allowed tend to grow
uncontrollably ;-)
If you want a bigger preamble, just use
Hi,
Vincent Beffara vbeff...@ens-lyon.fr writes:
Hi,
preamble sounds fine
As this seems to be the general consensus I've replaced prefix with
preamble as the header argument name
(and it would be excellent to allow for a code block as a preamble,
instead of a string in the header or as an
(Also worth mentioning that python 3 allows you to use actual unicode
characters inside strings in the file, not \xff chars; not sure if
org-babel needs to change its habits between python2 and python3?)
Vincent Beffara vbeff...@ens-lyon.fr writes:
#+begin_src python
# -*- coding: utf-8 -*-
s
Hi,
(and it would be excellent to allow for a code block as a preamble,
instead of a string in the header or as an alternative, because
preambles once they are allowed tend to grow uncontrollably ;-)
This is currently possible using the `sbe' function. Arbitrary emacs
lisp can be placed
Hi,
I've just pushed up a new prefix header argument. This header argument
only has meaning for python code blocks (since it is tied into
evaluation each language would have to handle it separately). This is
only used during external evaluation (i.e. not when :session is
specified) and the
Hi Vincent and Eric,
Vincent Beffara wrote:
I would suggest just trying it out first and seeing if you get an error
without such a line.
Well, I do, that's why I'm asking ;-)
Also, you could try adding the line to the beginning of your code
block.
I tried like this :
#+begin_src python
Hi Vincent and Eric,
Vincent Beffara wrote:
I would suggest just trying it out first and seeing if you get an error
without such a line.
Well, I do, that's why I'm asking ;-)
Also, you could try adding the line to the beginning of your code
block.
I tried like this :
#+begin_src python
#+begin_src python
# -*- coding: utf-8 -*-
s = é
#+end_src
I'm not sure to understand your problem. In fact, the problem is not
about inserting a prefix to the block, it's about the coding system
itself, I guess.
Your é in your Org buffer, how is it encoded? Is your Org buffer an
Hi,
I've just pushed up a new prefix header argument.
Fantastic ! It works exactly as needed. Thanks a lot !
This header argument only has meaning for python code blocks (since it
is tied into evaluation each language would have to handle it
separately).
That's fine, most cases can
Eric Schulte schulte.e...@gmail.com writes:
Hi,
I've just pushed up a new prefix header argument.
preamble might be a better name? or header? prefix makes me think of
adding a string onto the front of a string[1]; preamble and header are
used by e.g. latex to refer to prelimary lines at the
Dan Davison dandavis...@gmail.com writes:
Eric Schulte schulte.e...@gmail.com writes:
Hi,
I've just pushed up a new prefix header argument.
preamble might be a better name? or header? prefix makes me think of
adding a string onto the front of a string[1];
Absolutely, prefix was just the
Hi Eric and Dan,
Eric Schulte wrote:
Dan Davison dandavis...@gmail.com writes:
Eric Schulte schulte.e...@gmail.com writes:
I've just pushed up a new prefix header argument.
preamble might be a better name? or header? prefix makes me think of
adding a string onto the front of a string[1];
Hi,
I would suggest just trying it out first and seeing if you get an error
without such a line.
Well, I do, that's why I'm asking ;-)
Also, you could try adding the line to the beginning of your code
block.
I tried like this :
--8---cut
21 matches
Mail list logo