From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marc-Oliver Ihm <marc-oliver.ihm@online.de>
Subject: Re: [babel] Is there a way to use edebug on emacs-lisp code blocks ?
Date: Mon, 02 Jan 2012 14:41:23 +0100
Message-ID: <4F01B403.70108@online.de>
References: <jdpojo$bau$1@dough.gmane.org> <87mxa789y7.fsf@gmail.com>
	<4F00C9BF.7010504@online.de> <87ipkv82t5.fsf@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([140.186.70.92]:39656)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <marc-oliver.ihm@online.de>) id 1Rhi8l-00059s-OR
	for emacs-orgmode@gnu.org; Mon, 02 Jan 2012 08:41:28 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <marc-oliver.ihm@online.de>) id 1Rhi8k-0001lD-PU
	for emacs-orgmode@gnu.org; Mon, 02 Jan 2012 08:41:27 -0500
Received: from moutng.kundenserver.de ([212.227.126.187]:52606)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <marc-oliver.ihm@online.de>) id 1Rhi8k-0001l3-9W
	for emacs-orgmode@gnu.org; Mon, 02 Jan 2012 08:41:26 -0500
In-Reply-To: <87ipkv82t5.fsf@gmail.com>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=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: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org

Am 01.01.2012 23:40, schrieb Nicolas Goaziou:
> Marc-Oliver Ihm<marc-oliver.ihm@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 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 ?
> AFAIK, there is no such command.
>
>
> Regards,
>

Okay, thanx !

Than I will simply define an elisp-function and use edebug in that.

That's definitely fair enough for my case !
(but I will keep explicit edebug-support on my wishlist :-)

with kind regards, Marc-Oliver Ihm