From: Vitalie Spinu <spinuvit@gmail.com>
To: Michael Brand <michael.ch.brand@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>, Eric Schulte <schulte.eric@gmail.com>
Subject: Re: link abbreviation with multiple params, e. g. for geo locations
Date: Fri, 07 Jun 2013 21:54:50 +0200 [thread overview]
Message-ID: <87li6lelx1.fsf@gmail.com> (raw)
In-Reply-To: <CALn3zogvL86WmS2XNaiRUM-wEtL6_d5FMh0qNaaTOHbLy5X6fg@mail.gmail.com> (Michael Brand's message of "Fri, 7 Jun 2013 21:16:00 +0200")
>> Michael Brand <michael.ch.brand@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
next prev parent reply other threads:[~2013-06-07 19:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 17:03 link abbreviation with multiple params, e. g. for geo locations Michael Brand
2013-05-29 16:14 ` Michael Brand
2013-06-05 17:19 ` Michael Brand
2013-06-06 17:01 ` Eric Schulte
2013-06-07 14:53 ` Michael Brand
2013-06-07 15:18 ` Eric Schulte
2013-06-07 19:16 ` Michael Brand
2013-06-07 19:54 ` Vitalie Spinu [this message]
2013-06-08 18:05 ` Eric Schulte
2013-06-08 18:52 ` Vitalie Spinu
2013-06-08 19:21 ` Eric Schulte
2013-06-14 17:54 ` Michael Brand
2013-06-14 18:18 ` Eric Schulte
2013-06-14 20:13 ` Michael Brand
2013-06-19 9:39 ` Michael Brand
2013-06-07 20:10 ` Achim Gratz
2013-06-08 18:03 ` Eric Schulte
2013-06-09 7:56 ` Michael Brand
2013-06-09 8:07 ` Michael Brand
2013-06-09 19:18 ` Eric Schulte
2013-06-09 20:32 ` Michael Brand
2013-06-11 13:12 ` Eric Schulte
-- strict thread matches above, loose matches on Subject: below --
2013-05-05 15:06 Michael Brand
2013-05-06 7:06 ` Christian Moe
2013-05-06 18:42 ` Michael Brand
2013-05-06 22:29 ` Christian Moe
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=87li6lelx1.fsf@gmail.com \
--to=spinuvit@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=michael.ch.brand@gmail.com \
--cc=schulte.eric@gmail.com \
/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).