Re: [O] [PATCH] call_*() is not working inside #+DATE

2016-03-15 Thread Rafael Laboissiere
* Nicolas Goaziou [2016-03-15 19:50]: 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 strange, t

Re: [O] [PATCH] call_*() is not working inside #+DATE

2016-03-15 Thread Nicolas Goaziou
Hello, Rafael Laboissiere 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

Re: [O] [PATCH] call_*() is not working inside #+DATE

2016-03-15 Thread Rafael Laboissiere
* 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

Re: [O] [PATCH] call_*() is not working inside #+DATE

2016-03-14 Thread Nicolas Goaziou
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 b

Re: [O] [PATCH] call_*() is not working inside #+DATE

2016-03-14 Thread Rafael Laboissiere
* 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,

Re: [O] [PATCH] call_*() is not working inside #+DATE

2016-03-13 Thread Rafael Laboissiere
* Nicolas Goaziou [2016-03-13 18:24]: Rafael Laboissiere writes: 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 t

Re: [O] [PATCH] call_*() is not working inside #+DATE

2016-03-13 Thread Nicolas Goaziou
Hello, Rafael Laboissiere writes: > 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

Re: [O] [PATCH] call_*() is not working inside #+DATE

2016-03-12 Thread Rafael Laboissiere
* Eric S Fraga [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 a

Re: [O] [PATCH] call_*() is not working inside #+DATE

2016-03-12 Thread Eric S Fraga
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. -- : Eric S Fraga (0xFFFCF67D), Emacs 2

Re: [O] [PATCH] call_*() is not working inside #+DATE

2016-03-11 Thread Rafael Laboissiere
* Rafael Laboissiere [2016-03-07 02:58]: The following used to work for me in the past: #+NAME: date #+BEGIN_SRC sh :results silent :exports results :tangle no date #+END_SRC #+TITLE: Sample #+AUTHOR: Me #+DATE: call_date() and I saw the output of the shell command "date" when e