From: Nick Dokos <nicholas.dokos@hp.com>
To: Austin Frank <austin.frank@gmail.com>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: [babel] help debugging org-babel-execute-buffer
Date: Tue, 27 Jul 2010 00:41:00 -0400 [thread overview]
Message-ID: <18331.1280205660@gamaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Austin Frank <austin.frank@gmail.com> of "Mon, 26 Jul 2010 23:14:31 EDT." <m06301obu0.fsf@malibu.rochester.rr.com>
Austin Frank <austin.frank@gmail.com> wrote:
> I have a document that always throws an error when I call
> org-babel-execute-buffer. I'd guess that there's one particular block
> that is to blame, but I can't tell which block babel is in at the point
> when the error is thrown.
>
> The error is:
>
> #v+
> Debugger entered--Lisp error: (invalid-function org-save-outline-visibility)
> org-save-outline-visibility(t 1 nil nil)
> org-babel-execute-buffer(nil)
> call-interactively(org-babel-execute-buffer nil nil)
> #v-
>
> Looking at the macro for org-save-outline-visibility, I think the
> problem has to do with the last two arguments being passed in as nil
> nil. I don't, however, know how this is happening.
>
> I know that I probably haven't given enough information to actually
> diagnose this bug. Can anyone give me a hand on what my next debugging
> step should be for this problem?
>
Have you tried C-c C-c on each source block in the buffer? If one (or more)
fails, you know what to do.
If they all work fine, then I'd do a binary chop to get a minimal
example. Then edebug org-babel-execute-buffer on the minimal example
(if the macro causes problems with edebug, define a new function,
org-babel-execute-buffer-do-not-save-outline-visibility, which does not
invoke the macro and debug that: if that works, then there is probably
some funky interaction with the macro.) In each iteration of the loop,
record the beginning of the match and the end of the match: that'll tell
you which block is being executed.
The simplest solution of course is to send the whole thing to Eric
S. :-) [1]
HTH,
Nick
[1] http://www.snopes.com/college/exam/barometer.asp
next prev parent reply other threads:[~2010-07-27 4:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 3:14 [babel] help debugging org-babel-execute-buffer Austin Frank
2010-07-27 4:41 ` Nick Dokos [this message]
2010-07-27 6:33 ` Austin Frank
2010-08-19 5:33 ` Nick Dokos
2010-08-25 14:50 ` Eric Schulte
2010-08-27 14:21 ` Eric Schulte
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=18331.1280205660@gamaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=austin.frank@gmail.com \
--cc=emacs-orgmode@gnu.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).