From: "Eric Schulte" <schulte.eric@gmail.com>
To: nicholas.dokos@hp.com
Cc: emacs-orgmode@gnu.org
Subject: Re: [babel] help debugging org-babel-execute-buffer
Date: Fri, 27 Aug 2010 08:21:18 -0600 [thread overview]
Message-ID: <87wrrcxhk1.fsf@gmail.com> (raw)
In-Reply-To: <87d3t6d9wc.fsf@gmail.com> (Eric Schulte's message of "Wed, 25 Aug 2010 08:50:11 -0600")
This fix has now been applied. Best -- Eric
"Eric Schulte" <schulte.eric@gmail.com> writes:
> Hi Nick,
>
> Thanks for hunting this bug down.
>
> Nick Dokos <nicholas.dokos@hp.com> writes:
>
>> 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 think this is a bug: org-save-outline-visibility is indeed a macro,
>> defined in org.el, but ob.el does not require org.el, so when it is
>> compiled, the compiler thinks it's a function that will be defined elsewhere.
>> If the uncompiled ob.el is loaded, there should be no problem.
>>
>> Two possible solutions:
>>
>> - (require 'org) in ob.el.
>
> This first solution can't work, because org.el requires ob.el, and
> circular requires are not allowed.
>
>>
>> - move the definition of the macro to org-macs.el (which is required
>> by ob.el *and* org.el.)
>>
>> I'd vote for the second, but Carsten and/or Eric might have a different
>> preference.
>>
>
> I agree this sounds like a good solution, if Carsten agrees then I will
> apply it.
>
> Thanks -- Eric
>
>>
>> Nick
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Please use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
prev parent reply other threads:[~2010-08-27 14:21 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
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 [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=87wrrcxhk1.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.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).