Re: [Orgmode] Org-babel init

2010-07-13 Thread Jordi Inglada
Hi Eric, That worked. I am ready to go now! Thank you! Jordi Eric Schulte writes: Hi Jordi, The attached simple-init.el file works for me with emacs -Q -l simple-init.el Emacs started w/o error, and I was able to evaluate python code blocks with no problem. Please

[Orgmode] Org-babel init

2010-07-12 Thread Jordi Inglada
Hi all, I am having the same problem as this user here: http://www.mail-archive.com/emacs-orgmode@gnu.org/msg17498.html and the contrib/lisp directory is indeed in my load path. I am using a git changeset cloned today (Org-mode version 6.34trans (release_6.36.608.gc1ef)). I have tried using

Re: [Orgmode] Org-babel init

2010-07-12 Thread Erik Iverson
You need to see: http://eschulte.github.com/babel-dev/DONE-document-configuration-changes-for-Babel-integration.html Jordi Inglada wrote: Hi all, I am having the same problem as this user here: http://www.mail-archive.com/emacs-orgmode@gnu.org/msg17498.html and the contrib/lisp directory

Re: [Orgmode] Org-babel init

2010-07-12 Thread Eric Schulte
Hi Jordi, With the latest Org-mode from Git, Org-babel is now part of Org-mode, so you no longer need to add the contrib directory to your load path, or require org-babel-init. The following should work for you. (setq load-path (cons /home/inglada/local/src/org-mode/lisp load-path)) (require

Re: [Orgmode] Org-babel init

2010-07-12 Thread Jordi Inglada
Eric, Thanks for the answer. If I do that using emacs -q, I get this message when loading the configuration: Symbol's value as variable is void: org-babel-tangle-lang-exts An after that when trying to evaluate this block from the tutorial #+begin_src python import time print(Hello, today's

Re: [Orgmode] Org-babel init

2010-07-12 Thread Eric Schulte
Hi Jordi, The attached simple-init.el file works for me with emacs -Q -l simple-init.el Emacs started w/o error, and I was able to evaluate python code blocks with no problem. Please give it a try and let me know if it doesn't work -- Eric (note you'll have to update the path to org/lisp)