From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: [PATCH] call_*() is not working inside #+DATE Date: Mon, 14 Mar 2016 20:41:07 +0100 Message-ID: <87vb4okfu4.fsf@nicolasgoaziou.fr> References: <20160307015829.GE11627@laboissiere.net> <20160312075704.GI16308@laboissiere.net> <20160314164354.GK3916@laboissiere.net> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:35283) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1afYKY-00039H-UJ for emacs-orgmode@gnu.org; Mon, 14 Mar 2016 15:39:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1afYKU-0000jC-PR for emacs-orgmode@gnu.org; Mon, 14 Mar 2016 15:39:06 -0400 Received: from relay4-d.mail.gandi.net ([217.70.183.196]:35914) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1afYKU-0000j4-J4 for emacs-orgmode@gnu.org; Mon, 14 Mar 2016 15:39:02 -0400 In-Reply-To: <20160314164354.GK3916@laboissiere.net> (Rafael Laboissiere's message of "Mon, 14 Mar 2016 17:43:54 +0100") 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: Rafael Laboissiere Cc: emacs-orgmode@gnu.org Hello, Rafael Laboissiere writes: > * Rafael Laboissiere [2016-03-12 08:57]: >> >> [snip] >> >> I investigated this issue further and discovered that the constructs >> call_(args) and src_{code} are not evaluated at all when >> they appear in a keyword line (starting with "#+:"). >> Org-babel behaves in this way probably on purpose. At any rate, it >> would be better if the current behavior is documented somewhere. >> This may be accomplished with the patch attached below. > > I went ahead and committed the patch. I think this is a bit premature, as we're still discussing how to fix this issue, so this documentation patch is likely to be removed soon. Moreover, I don't think the problem doesn't appear on maint branch, where you applied your patch. So, at the very least, it should be removed from there. Regards, -- Nicolas Goaziou