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: Tue, 15 Mar 2016 19:50:29 +0100 [thread overview]
Message-ID: <87bn6finii.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <20160315102358.GU3916@laboissiere.net> (Rafael Laboissiere's message of "Tue, 15 Mar 2016 11:23:58 +0100")
Hello,
Rafael Laboissiere <rafael@laboissiere.net> writes:
> 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 […]".
The problem is that the documentation patch is (partly) wrong. From
maint, you can try calling `org-babel-execute-buffer' in the following
document
#+DATE: src_emacs-lisp{(+ 1 1)}
It is possible to evaluate code snippets in keywords. It is not
possible, AFAIR, to evaluate them during export.
> The problem affects both master and maint, currently.
See above. I don't see the point of documenting a bug. It doesn't help
fixing it. Anyway, it's a minor issue. Let's not waste too much time on
this.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2016-03-15 18:48 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
2016-03-15 10:23 ` Rafael Laboissiere
2016-03-15 18:50 ` Nicolas Goaziou [this message]
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bn6finii.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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).