>> Michael Brand <michael.ch.br...@gmail.com>
>> on Fri, 7 Jun 2013 21:16:00 +0200 wrote:
[...]
>>
>> 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.
[...]
> 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?
I named it with "head" because head is the local variable in
org-babel-get-src-block-info referring to that position. There are
other functions that use -head: org-babel-goto-src-block-head,
org-babel-where-is-src-block-head.
But, I agree that it might be better called beg, location or position.
I think "src-block" is not misleading, there are plenty of
foo-src-block-bar in babel.
May be then: org-babel-current-src-block-location?
The -exec- part stands for -executed- and, might be drop.
It should be explicitly named because this is a global variable which is
bound only during the processing of src-blocks, simply 'loc wouldn't
work.
Vitalie
