Am 01.01.2012 23:40, schrieb Nicolas Goaziou:
Marc-Oliver Ihmmarc-oliver@online.de writes:
So, if I have something like:
#+call: foo(1,2)
I cannot see a way to get a buffer with all the code, that foo might
expand into, INCLUDING the assignments for the arguments 1 and 2.
(If babel
Hi 2012, hi all !
Is there a way to use edebug for debugging my emacs-lisp code blocks ?
(Or is there another preferred way to debug emacs-lisp code in babel ?)
For normal coding I use edebug a lot and it would be great to be able to use it
in babel too.
The only workaround I can currently
Am 01.01.2012 21:05, schrieb Nicolas Goaziou:
Hello,
Marc-Oliver Ihmmarc-oliver@online.de writes:
Is there a way to use edebug for debugging my emacs-lisp code blocks ?
(Or is there another preferred way to debug emacs-lisp code in
babel ?)
You can open the block in a temporary buffer,
Marc-Oliver Ihm marc-oliver@online.de writes:
So, if I have something like:
#+call: foo(1,2)
I cannot see a way to get a buffer with all the code, that foo might
expand into, INCLUDING the assignments for the arguments 1 and 2.
(If babel would give me such a buffer, than it would be
