Thanks for the suggestion Nick,
I've moved the macro definition up towards the top of ob.el, and for
good measure I am now autoloading it. After this change I am able to
call both ob-execute-subtree and ob-execute-buffer without error on the
following simple Org-mode file
* top
** first
On 19 Nov 2010, at 09:19, Eric Schulte wrote:
Could you and/or Konrad let me know if this now works on your systems,
and if not could you send me an example file that exercises the error?
It works fine now!
Thanks,
Konrad.
___
Emacs-orgmode
On 18 Nov 2010, at 01:07, Eric Schulte wrote:
Thanks for doing most of the debugging on this.
After much banging of my head, I stumbled onto this very nice page of
common problems with compiled Macros in Emacs Lisp [1], it looks like
this sort of thing has happened before. :)
I realized I was
Eric Schulte schulte.e...@gmail.com wrote:
Thanks for doing most of the debugging on this.
After much banging of my head, I stumbled onto this very nice page of
common problems with compiled Macros in Emacs Lisp [1], it looks like
this sort of thing has happened before. :)
I realized I
Thanks for doing most of the debugging on this.
After much banging of my head, I stumbled onto this very nice page of
common problems with compiled Macros in Emacs Lisp [1], it looks like
this sort of thing has happened before. :)
I realized I was guilty of one of the macro sins specified above,
At Mon, 08 Nov 2010 09:45:25 -0500,
Nick Dokos wrote:
Something to do with the compilation of the org-babel-map-src-blocks
macro, no doubt. I don't see it with uncompiled files.
Not a solution, but some debugging showed that
`org-babel-get-src-block-info' fails to get the info of the source
On 02.11.2010, at 17:09, Ista Zahn wrote:
I recently upgraded to version 7.3 (from 7.01), and discovered that
org-babel-execute-buffer no longer works, returning Wrong type
argument: consp, nil.
I just ran into the same problem... Did you find a workaround, other than going
back to some
I'm unable to re-create this problem. Could you please send a minimal
example file in which the problem occurs?
Thanks -- Eric
Konrad Hinsen konrad.hin...@fastmail.net writes:
On 02.11.2010, at 17:09, Ista Zahn wrote:
I recently upgraded to version 7.3 (from 7.01), and discovered that
On 08.11.2010, at 14:49, Eric Schulte wrote:
I'm unable to re-create this problem. Could you please send a minimal
example file in which the problem occurs?
Here is an example file. Open it and run org-babel-execute-buffer, and you will
get Wrong type argument: consp, nil. Then type C-c C-c
Konrad Hinsen konrad.hin...@fastmail.net writes:
On 08.11.2010, at 14:49, Eric Schulte wrote:
I'm unable to re-create this problem. Could you please send a minimal
example file in which the problem occurs?
Here is an example file. Open it and run org-babel-execute-buffer, and you
will
Konrad Hinsen konrad.hin...@fastmail.net wrote:
On 08.11.2010, at 14:49, Eric Schulte wrote:
I'm unable to re-create this problem. Could you please send a minimal
example file in which the problem occurs?
Here is an example file. Open it and run org-babel-execute-buffer, and
you will
On 08.11.2010, at 15:45, Nick Dokos wrote:
Konrad Hinsen konrad.hin...@fastmail.net wrote:
On 08.11.2010, at 14:49, Eric Schulte wrote:
I'm unable to re-create this problem. Could you please send a minimal
example file in which the problem occurs?
Here is an example file. Open it and
Hi,
I recently upgraded to version 7.3 (from 7.01), and discovered that
org-babel-execute-buffer no longer works, returning Wrong type
argument: consp, nil. This behavior is exists even with the simplest
of examples, such as
#+begin_src R
2+2
#+end_src
and persists even when I reduce my .emacs
13 matches
Mail list logo
