From: Rafael Laboissiere <rafael@laboissiere.net>
To: emacs-orgmode@gnu.org
Subject: Re: [PATCH] call_*() is not working inside #+DATE
Date: Sat, 12 Mar 2016 10:34:51 +0100 [thread overview]
Message-ID: <20160312093451.GL16308@laboissiere.net> (raw)
In-Reply-To: <877fh8oz9g.fsf@ucl.ac.uk>
* Eric S Fraga <e.fraga@ucl.ac.uk> [2016-03-12 08:51]:
> On Saturday, 12 Mar 2016 at 08:57, Rafael Laboissiere wrote:
>> P.S.: For those who are reading this message and are interested in a
>> solution for my original problem, here is the way I am getting around it
>> right now.
>
> Thanks for this alternate solution.
You are welcome.
It would be much better if the following construct worked:
#+DATE: src_sh{git show -s --date=short --format="%cd [%h]" HEAD}
Unfortunately, it does not. This behavior (or misbehavior, I do not
know) can be traced down to the org-element-context function. Suppose
that you have the following content in a org-mode buffer:
#+DATE: src_sh{date}
src_sh{date}
With the cursor just after the underscore in the #+DATE line,
org-element-context returns:
(keyword
(:key "DATE" :value "src_sh{date}" :begin 1 :end 22 :post-blank 0 :post-affiliated 1 :parent nil))
On the other hand, with the cursor just after the underscore in the next
line, org-element-context returns (as it should be):
(inline-src-block
(:language "sh" :value "date" :parameters nil :begin 22 :end 34 :post-blank 0
:parent (paragraph (:begin 22 :end 35 :contents-begin 22 :contents-end 35 :post-blank 0
:post-affiliated 22 :parent nil))))
This is the reason why Org-babel does not evaluate the inline source
block in the #+DATE line.
Best,
Rafael Laboissière
next prev parent reply other threads:[~2016-03-12 9:34 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 [this message]
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
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=20160312093451.GL16308@laboissiere.net \
--to=rafael@laboissiere.net \
--cc=emacs-orgmode@gnu.org \
/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).