From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rafael Laboissiere Subject: Re: [PATCH] call_*() is not working inside #+DATE Date: Tue, 15 Mar 2016 11:23:58 +0100 Message-ID: <20160315102358.GU3916@laboissiere.net> References: <20160307015829.GE11627@laboissiere.net> <20160312075704.GI16308@laboissiere.net> <20160314164354.GK3916@laboissiere.net> <87vb4okfu4.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59862) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1afm8y-00057P-64 for emacs-orgmode@gnu.org; Tue, 15 Mar 2016 06:24:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1afm8u-0003RO-6e for emacs-orgmode@gnu.org; Tue, 15 Mar 2016 06:24:04 -0400 Received: from laboissiere.net ([46.101.243.132]:48972) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1afm8t-0003R9-VA for emacs-orgmode@gnu.org; Tue, 15 Mar 2016 06:24:00 -0400 Content-Disposition: inline In-Reply-To: <87vb4okfu4.fsf@nicolasgoaziou.fr> 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 * Nicolas Goaziou [2016-03-14 20:41]: > Rafael Laboissiere writes: > >> * Rafael Laboissiere [2016-03-12 08:57]: >>> >>> [snip] >>> >> 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. Hopefully, a solution will be found soon and the documentation will be adjusted accordingly. Notice that, in section "Evaluating code blocks", it is written "It is also possible to evaluate named code blocks from anywhere […]". > 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. The problem affects both master and maint, currently. Rafael Laboissière