[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] link abbreviation with multiple params, e. g. for geo locations
From: |
Michael Brand |
Subject: |
Re: [O] link abbreviation with multiple params, e. g. for geo locations |
Date: |
Fri, 14 Jun 2013 19:54:04 +0200 |
Hi Eric
On Sat, Jun 8, 2013 at 9:21 PM, Eric Schulte <address@hidden> wrote:
> Vitalie Spinu <address@hidden> writes:
>> [...]
>> `org-babel-src-block-location'
>>
>> or probably even more suggestive:
>>
>> `org-babel-src-block-beginning'.
>>
>
> I like "current" because it is similar to other variables which are
> dynamically bound by Org-mode and without it there is no indication that
> it points to a block which is active *now*.
>
> I've changed the variable name to your previous suggestion of
> `org-babel-current-src-block-location'.
Thanks to all for the clarifications about the name and the improved
docstring of org-babel-current-src-block-location. Now I see the good
reasons for the old and the new name.
According to this change and my better understanding I am rewriting
and extending the ERT from my previous patch to document my use case.
There is an issue with shell and :session that I do not know how to
deal with: In the following example when I do "C-c C-c" on #+BEGIN_SRC
the result is as expected but on the "#+CALL" lines it should be
: a:0
and
: a:1
The :session is only to have more than one call which works for
emacs-lisp source blocks. Am I doing something wrong or is this a bug?
------------------------------------------------------------
#+NAME: func
#+HEADER: :var a=(or (org-entry-get
org-babel-current-src-block-location "a" t) "0")
#+BEGIN_SRC sh :shebang #!/bin/sh :results verbatim
echo "a:$a"
#+END_SRC
#+RESULTS: func
: a:0
#+CALL: func[:session default]()
#+RESULTS: func[:session default]()
:
: > > ^[]0;^Gbash-3.2$ a:0
* section
:PROPERTIES:
:a: 1
:END:
#+CALL: func[:session property]()
#+RESULTS: func[:session property]()
:
: > > ^[]0;^Gbash-3.2$ a:1
------------------------------------------------------------
Michael
- Re: [O] link abbreviation with multiple params, e. g. for geo locations, Michael Brand, 2013/06/05
- Re: [O] link abbreviation with multiple params, e. g. for geo locations, Eric Schulte, 2013/06/06
- Re: [O] link abbreviation with multiple params, e. g. for geo locations, Michael Brand, 2013/06/07
- Re: [O] link abbreviation with multiple params, e. g. for geo locations, Eric Schulte, 2013/06/07
- Re: [O] link abbreviation with multiple params, e. g. for geo locations, Michael Brand, 2013/06/07
- Re: [O] link abbreviation with multiple params, e. g. for geo locations, Vitalie Spinu, 2013/06/07
- Re: [O] link abbreviation with multiple params, e. g. for geo locations, Eric Schulte, 2013/06/08
- Re: [O] link abbreviation with multiple params, e. g. for geo locations, Vitalie Spinu, 2013/06/08
- Re: [O] link abbreviation with multiple params, e. g. for geo locations, Eric Schulte, 2013/06/08
- Re: [O] link abbreviation with multiple params, e. g. for geo locations,
Michael Brand <=
- Re: [O] link abbreviation with multiple params, e. g. for geo locations, Eric Schulte, 2013/06/14
- Re: [O] link abbreviation with multiple params, e. g. for geo locations, Michael Brand, 2013/06/14
- Re: [O] link abbreviation with multiple params, e. g. for geo locations, Michael Brand, 2013/06/19
- Re: [O] link abbreviation with multiple params, e. g. for geo locations, Achim Gratz, 2013/06/07
- Re: [O] link abbreviation with multiple params, e. g. for geo locations, Eric Schulte, 2013/06/08
- Re: [O] link abbreviation with multiple params, e. g. for geo locations, Michael Brand, 2013/06/09
- Re: [O] link abbreviation with multiple params, e. g. for geo locations, Michael Brand, 2013/06/09
- Re: [O] link abbreviation with multiple params, e. g. for geo locations, Eric Schulte, 2013/06/09
- Re: [O] link abbreviation with multiple params, e. g. for geo locations, Michael Brand, 2013/06/09
- Re: [O] link abbreviation with multiple params, e. g. for geo locations, Eric Schulte, 2013/06/11