From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Rafael Laboissiere <rafael@laboissiere.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] call_*() is not working inside #+DATE
Date: Mon, 14 Mar 2016 20:41:07 +0100 [thread overview]
Message-ID: <87vb4okfu4.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <20160314164354.GK3916@laboissiere.net> (Rafael Laboissiere's message of "Mon, 14 Mar 2016 17:43:54 +0100")
Hello,
Rafael Laboissiere <rafael@laboissiere.net> writes:
> * Rafael Laboissiere <rafael@laboissiere.net> [2016-03-12 08:57]:
>>
>> [snip]
>>
>> I investigated this issue further and discovered that the constructs
>> call_<name>(args) and src_<lang>{code} are not evaluated at all when
>> they appear in a keyword line (starting with "#+<keyword>:").
>> 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
next prev parent reply other threads:[~2016-03-14 19:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 1:58 call_*() is not working inside #+DATE Rafael Laboissiere
2016-03-12 7:57 ` [PATCH] " Rafael Laboissiere
2016-03-12 8:51 ` Eric S Fraga
2016-03-12 9:34 ` Rafael Laboissiere
2016-03-13 17:24 ` Nicolas Goaziou
2016-03-13 17:41 ` Rafael Laboissiere
2016-03-14 16:43 ` Rafael Laboissiere
2016-03-14 19:41 ` Nicolas Goaziou [this message]
2016-03-15 10:23 ` Rafael Laboissiere
2016-03-15 18:50 ` Nicolas Goaziou
2016-03-15 20:58 ` Rafael Laboissiere
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vb4okfu4.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=rafael@laboissiere.net \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.