This fix has now been applied. Best -- Eric
"Eric Schulte" writes:
> Hi Nick,
>
> Thanks for hunting this bug down.
>
> Nick Dokos writes:
>
>> Austin Frank wrote:
>>
>>
>>> I have a document that always throws an error when I call
>>> org-babel-execute-buffer. I'd guess that there's one par
Hi Nick,
Thanks for hunting this bug down.
Nick Dokos writes:
> Austin Frank 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 po
Austin Frank 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 en
Austin Frank 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 ent
Hello!
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-funct
