emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Marc-Oliver Ihm <marc-oliver.ihm@online.de>
To: emacs-orgmode@gnu.org
Subject: Re: [babel] Is there a way to use edebug on emacs-lisp code blocks ?
Date: Sun, 01 Jan 2012 22:01:51 +0100	[thread overview]
Message-ID: <4F00C9BF.7010504@online.de> (raw)
In-Reply-To: <87mxa789y7.fsf@gmail.com>

Am 01.01.2012 21:05, schrieb Nicolas Goaziou:
> Hello,
>
> Marc-Oliver Ihm<marc-oliver.ihm@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, with C-c ', and use C-u
> C-M-x from there.
>
>
> Regards,
>

Hi Nicolas,

Thanx, that is close ! However, I also need to resolve <<noweb>> references.

Resolving <<noweb>> references is something, that org-babel-expand-src-block does,
which however is still not what I need, because it only works for #+begin_src ... #+end_src blocks,
but not for #+call: lines and for the arguments, which can be passed.

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 easy to use edebug on it, I agree.)

So, to be more precise: Is there any command that would expand a full #+call: line like above
with all its arguments into pure elisp ?

Thanx for your help !

next prev parent reply	other threads:[~2012-01-01 21:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-01 13:55 [babel] Is there a way to use edebug on emacs-lisp code blocks ? Marc-Oliver Ihm
2012-01-01 20:05 ` Nicolas Goaziou
2012-01-01 21:01   ` Marc-Oliver Ihm [this message]
2012-01-01 22:40     ` Nicolas Goaziou
2012-01-02 13:41       ` Marc-Oliver Ihm

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=4F00C9BF.7010504@online.de \
    --to=marc-oliver.ihm@online.de \
    --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

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).