From: Mark Stoehr <stoehr@cs.uchicago.edu>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Getting source code to work
Date: Wed, 1 Aug 2012 14:11:38 -0500 [thread overview]
Message-ID: <CAPLV0cjD5vJFDw=ND15RR=UD1qJhtoCoBn16UXXUzyA6HXKLDQ@mail.gmail.com> (raw)
In-Reply-To: <m1vch24ejk.fsf@tsdye.com>
Thanks Tom,
I do have
(org-babel-do-load-languages
'org-babel-load-languages '((python . t)
(R . t)))
in my ~/.emacs.d/init.el
and my version (from M-x org-version) is
Org-mode version 7.8.11
Cheers,
Mark
On Wed, Aug 1, 2012 at 2:07 PM, Thomas S. Dye <tsd@tsdye.com> wrote:
> Aloha Mark,
>
> Mark Stoehr <stoehr@cs.uchicago.edu> writes:
>
>> Hi, I'm trying to include python source code in my document and I'm
>> finding that org-babel-execute-buffer ( as well as C-c C-c at the end
>> of a code block) does not successfully run my code, instead I get an
>> error "Invalid function: org-save-outline-visibility". I saw messages
>> earlier
>>
>> http://thread.gmane.org/gmane.emacs.orgmode/28048/focus=28049
>>
>> regarding an apparently similar problem but my understanding of emacs
>> lisp is insufficient for me to make sense of it. My program:
>>
>> #+BEGIN_SRC python
>> print "Hello World"
>> return 1+2
>> #+END_SRC
>>
>>
>> I also have trouble getting tangle to work. With the following problem
>>
>>
>> #+BEGIN_SRC python :tangle yes
>> print "Hello World"
>> return 1+2
>> #+END_SRC
>>
>> both C-c C-v t and M-x org-babel-tangle fail saying that 0 blocks have
>> been tangled. I also tried the examples with the #+BEGIN_SRC and
>> #+END_SRC being in lowercase and that didn't change anything.
>>
>>
>
> Your source code block evaluates fine on my setup:
>
> #+BEGIN_SRC python
> print "Hello World"
> return 1+2
> #+END_SRC
>
> #+RESULTS:
> : 3
>
> The error message you are getting refers to a bug that was apparently
> fixed some time ago. What version of Org mode are you running?
>
> Also, did you tell Org mode that you will be evaluating Python code?
> You should have something like this in .emacs:
>
> (org-babel-do-load-languages
> 'org-babel-load-languages
> '((R . t)
> (C . t)
> (ditaa . t)
> (dot . t)
> (emacs-lisp . t)
> (gnuplot . nil)
> (haskell . nil)
> (latex . t)
> (lisp . t)
> (ocaml . nil)
> (org . t)
> (perl . t)
> (python . t) # This is the line you'll need
> (ruby . nil)
> (screen . nil)
> (sh . t)
> (sql . nil)
> (sqlite . t)))
>
> hth,
> Tom
>
> --
> Thomas S. Dye
> http://www.tsdye.com
>
next prev parent reply other threads:[~2012-08-01 19:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 18:51 Getting source code to work Mark Stoehr
2012-08-01 19:07 ` Thomas S. Dye
2012-08-01 19:11 ` Mark Stoehr [this message]
2012-08-01 19:48 ` Thomas S. Dye
2012-08-01 22:27 ` Rasmus
2012-08-01 19:11 ` Nick Dokos
2012-08-01 19:18 ` Mark Stoehr
2012-08-01 19:58 ` Eric Schulte
2012-08-01 20:00 ` Nick Dokos
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='CAPLV0cjD5vJFDw=ND15RR=UD1qJhtoCoBn16UXXUzyA6HXKLDQ@mail.gmail.com' \
--to=stoehr@cs.uchicago.edu \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.com \
/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).