From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marc-Oliver Ihm Subject: Re: [babel] Is there a way to use edebug on emacs-lisp code blocks ? Date: Sun, 01 Jan 2012 22:01:51 +0100 Message-ID: <4F00C9BF.7010504@online.de> References: <87mxa789y7.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([140.186.70.92]:39926) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RhSXh-0007ju-UD for emacs-orgmode@gnu.org; Sun, 01 Jan 2012 16:02:10 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RhSXg-0001PI-J6 for emacs-orgmode@gnu.org; Sun, 01 Jan 2012 16:02:09 -0500 Received: from lo.gmane.org ([80.91.229.12]:56812) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RhSXg-0001PA-Bi for emacs-orgmode@gnu.org; Sun, 01 Jan 2012 16:02:08 -0500 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1RhSXd-0001gT-VW for emacs-orgmode@gnu.org; Sun, 01 Jan 2012 22:02:05 +0100 Received: from p54a88102.dip0.t-ipconnect.de ([84.168.129.2]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 01 Jan 2012 22:02:05 +0100 Received: from marc-oliver.ihm by p54a88102.dip0.t-ipconnect.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 01 Jan 2012 22:02:05 +0100 In-Reply-To: <87mxa789y7.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Am 01.01.2012 21:05, schrieb Nicolas Goaziou: > Hello, > > Marc-Oliver Ihm 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 <> references. Resolving <> 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 !