From: Nick Dokos <nicholas.dokos@hp.com>
To: Mark Stoehr <stoehr@cs.uchicago.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: Getting source code to work
Date: Wed, 01 Aug 2012 16:00:45 -0400 [thread overview]
Message-ID: <4259.1343851245@alphaville> (raw)
In-Reply-To: Message from Mark Stoehr <stoehr@cs.uchicago.edu> of "Wed, 01 Aug 2012 14:18:43 CDT." <CAPLV0ciUmeqX96RQY91Q8cMq-p8itK=eTi1EYxT27Lvaxsd09g@mail.gmail.com>
Mark Stoehr <stoehr@cs.uchicago.edu> wrote:
> I just installed emacs and org-mode on a new machine, do you have any
> suggestions for debugging this?
>
No easy way, I'm afraid (but maybe somebody else can think of something
better). I usually run edebug on the suspect function and single step
through it, examining variables as I go.
For details on edebug, see the emacs lisp manual, section 18.2 "Edebug".
Nick
> Mark
>
> On Wed, Aug 1, 2012 at 2:11 PM, Nick Dokos <nicholas.dokos@hp.com> wrote:
> > Mark Stoehr <stoehr@cs.uchicago.edu> wrote:
> >
> >> 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.
> >>
> >
> > Cannot reproduce either problem: the code block produces a
> >
> > #+RESULTS:
> > : 3
> >
> > and the tangle says:
> >
> > tangled 1 code block from mark-stoehr.org
> >
> > Nick
> >
> > Version info:
> >
> > Org-mode version 7.8.11 (release_7.8.11-260-ga15b7d @ /home/nick/elisp/org-mode/lisp/)
> > (includes a few local commits)
> >
> > GNU Emacs 24.1.50.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.24.4) of 2012-07-28
> >
>
prev parent reply other threads:[~2012-08-01 20:00 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
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 [this message]
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=4259.1343851245@alphaville \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=stoehr@cs.uchicago.edu \
/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).