Re: [O] link abbreviation with multiple params, e. g. for geo locations

[Michael Brand]

Hi Eric

On Fri, Jun 7, 2013 at 5:18 PM, Eric Schulte <address@hidden> wrote:
>> In this commit I see two issues which my patch does not have:
>>
>> 1) The variable name org-babel-current-exec-src-block-head is the same
>>    as for a different meaning (source block head) and purpose introduced
>>    in release_8.0.3-202-gf301bbc
>>
>>        commit f301bbcc862c2acc61749bc1e24895bf69cd4d06
>>        Author: Vitalie Spinu <address@hidden>
>>        Date:   Thu Jun 6 12:04:02 2013 +0200
>>
>>            make src block location available to execution backends
>>
>>    but in release_8.0.3-207-g5dc5143 the same name is used for the
>>    point-marker of "call_func" which is misleading.
>
> Perhaps the variable name should be updated, but this extension is
> simply a generalization to include inline code blocks as well.  I don't
> find it misleading.

Aha, now it seems to me that I must have misunderstood the variable
name org-babel-current-exec-src-block-head as introduced with the
first commit release_8.0.3-202-gf301bbc. Because of the "src-block"
and "head" in the name and because this commit was made for debugging
I thought that the variable refers to point-marker of the one and only
named code block with the #+HEADER, in my thinking the "function
definition" to be debugged.

Is this understanding wrong and the variable refers to point-marker of
just every code block evaluation individually, not only in the changes
for release_8.0.3-207-g5dc5143 but also in the changes for
release_8.0.3-202-gf301bbc ?

If yes then I understand only now that the functionality of the new
variable is of course the same for the changes in both commits and
therefore the name has to be the same for the changes in both commits.
But for me it would have helped to have some other name, containing
neither "src-block", which I associate it with #+BEGIN_SRC but
not #+CALL line or inline call_<name>, nor "head", which I associate
with #+HEADER. I would like to suggest org-babel-exec-marker. What do
you and Vitalie (CCed) think?

>> 2) Export is not supported ("C-c C-c" works as expected).
>
> I can't reproduce this bug.

>From your attached org-entry-get-point-example.org I get with some
lines omitted

\section{example of a geo location, realistic to try out}
\item \texttt{geo\_var is 4.56,7.89} \texttt{geo\_var is 4.56,7.89}
\section{another geo location}
\item \texttt{geo\_var is 4.56,7.89} \texttt{geo\_var is 4.44,5.55}

but expect

\section{example of a geo location, realistic to try out}
\item \texttt{geo\_var is 4.56,7.89} \texttt{geo\_var is 4.56,7.89}
\section{another geo location}
\item \texttt{geo\_var is 4.44,5.55} \texttt{geo\_var is 4.44,5.55}

Changing to

#+HEADER: :var geo_var=(format "%s" org-babel-current-exec-src-block-head)

shows that the variable is nil.

> The following Org-mode file.
>
> exports to the following latex

>From your attached export-loc.org I get the same evaluations after
uncommenting "#+PROPERTY: exports results"

Michael