[...]
>
> This is in branch ob-inherit at
> https://github.com/dandavison/org-devel. I've given you write access to
> the repo. The branch isn't ready to go yet, just a first
> pass. Currently, with this file
>
> -
> #+property: var a=1
> #+property: var b=2
>
>
"Eric Schulte" writes:
> [...]
>>> Maybe we could extend the :var header argument to support the following
>>> syntax...
>>>
>>> #+begin_src emacs-lisp :var A=1 B=3
>>> ;; code
>>> #+end_src
>>>
>>> or
>>>
>>> ** two vars in a properties block
>>>:PROPERTIES:
>>>:var: test1=7 test2
Dan Davison writes:
> "Eric Schulte" writes:
>
>> [...]
>>>
>>> I agree, the things I was talking about don't end up being simpler in
>>> terms of usage for this case. My thinking was that variable unsetting
>>> might be something that would be required fairly rarely, and so it might
>>> be wort
[...]
>> Maybe we could extend the :var header argument to support the following
>> syntax...
>>
>> #+begin_src emacs-lisp :var A=1 B=3
>> ;; code
>> #+end_src
>>
>> or
>>
>> ** two vars in a properties block
>>:PROPERTIES:
>>:var: test1=7 test2=8
>>:END:
>>
>> That shouldn't be
"Eric Schulte" writes:
> [...]
>>
>> I agree, the things I was talking about don't end up being simpler in
>> terms of usage for this case. My thinking was that variable unsetting
>> might be something that would be required fairly rarely, and so it might
>> be worth appropriate to support it as
"Eric Schulte" writes:
> [...]
>>> It seems that what you want to do can be described as disabling
>>> inheritance of the :var properties for a specific block.
>>
>> Agreed - that would solve my problem.
>>
>>> So I'm suggesting that it may be more parsimonious to do this with
>>> the existing O
[...]
>
> I agree, the things I was talking about don't end up being simpler in
> terms of usage for this case. My thinking was that variable unsetting
> might be something that would be required fairly rarely, and so it might
> be worth appropriate to support it as part of a more general/powerful
[...]
>> It seems that what you want to do can be described as disabling
>> inheritance of the :var properties for a specific block.
>
> Agreed - that would solve my problem.
>
>> So I'm suggesting that it may be more parsimonious to do this with
>> the existing Org inheritance mechanisms than to
Dan Davison writes:
> [...]
>>> 2. It should be possible somehow to include the options together with
>>>the shebang, or to replace :shebang with a more general "preamble"
>>>concept. Or to make :shebang accept a code block as its value.
>>>
>>> --
Hi Dan,
Many interesting suggestions, but I don't see how any of them are
simpler (either conceptually or in terms of implementation) than
defining a way to "unset" a variable previously set at a higher level of
generality. Is it the concept or the syntax of the previous suggestions
that you find
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/11/2011 02:49 PM, Dan Davison wrote:
> [...]
>>> 2. It should be possible somehow to include the options together with
>>>the shebang, or to replace :shebang with a more general "preamble"
>>>concept. Or to make :shebang accept a code blo
"Eric Schulte" writes:
> Hi Dan,
>
> Many interesting suggestions, but I don't see how any of them are
> simpler (either conceptually or in terms of implementation) than
> defining a way to "unset" a variable previously set at a higher level of
> generality. Is it the concept or the syntax of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/11/2011 02:41 PM, Dan Davison wrote:
> Rainer M Krug writes:
>
>> On 02/11/2011 01:19 PM, Dan Davison wrote:
>>> "Eric Schulte" writes:
>>>
Rainer M Krug writes:
> On 02/10/2011 02:27 AM, Eric Schulte wrote:
>> Rainer M Krug
[...]
>> 2. It should be possible somehow to include the options together with
>>the shebang, or to replace :shebang with a more general "preamble"
>>concept. Or to make :shebang accept a code block as its value.
>>
>>
>> #+BABEL: :var A=13
>> #
Rainer M Krug writes:
> On 02/11/2011 01:19 PM, Dan Davison wrote:
>> "Eric Schulte" writes:
>>
>>> Rainer M Krug writes:
>>>
On 02/10/2011 02:27 AM, Eric Schulte wrote:
> Rainer M Krug writes:
>
>> Hi
>>
>> For one project, I am usinr org to write submit scripte to a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/11/2011 01:19 PM, Dan Davison wrote:
> "Eric Schulte" writes:
>
>> Rainer M Krug writes:
>>
>>> On 02/10/2011 02:27 AM, Eric Schulte wrote:
Rainer M Krug writes:
> Hi
>
> For one project, I am usinr org to write submit s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/11/2011 12:55 PM, Dan Davison wrote:
> Rainer M Krug writes:
>
>> On 02/11/2011 10:32 AM, Dan Davison wrote:
>>> Rainer M Krug writes:
>>>
On 02/10/2011 05:48 PM, Eric Schulte wrote:
> Rainer M Krug writes:
>
>> On 02/10/2011
"Eric Schulte" writes:
> Rainer M Krug writes:
>
>> On 02/10/2011 02:27 AM, Eric Schulte wrote:
>>> Rainer M Krug writes:
>>>
Hi
For one project, I am usinr org to write submit scripte to a cluster
runing torqu. The important bit in this is, that between the shebang and
Rainer M Krug writes:
> On 02/11/2011 10:32 AM, Dan Davison wrote:
>> Rainer M Krug writes:
>>
>>> On 02/10/2011 05:48 PM, Eric Schulte wrote:
Rainer M Krug writes:
> On 02/10/2011 02:27 AM, Eric Schulte wrote:
>> Rainer M Krug writes:
>>
>>> Hi
>>>
>>> For on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/11/2011 10:32 AM, Dan Davison wrote:
> Rainer M Krug writes:
>
>> On 02/10/2011 05:48 PM, Eric Schulte wrote:
>>> Rainer M Krug writes:
>>>
On 02/10/2011 02:27 AM, Eric Schulte wrote:
> Rainer M Krug writes:
>
>> Hi
>>
>>
Rainer M Krug writes:
> On 02/10/2011 05:48 PM, Eric Schulte wrote:
>> Rainer M Krug writes:
>>
>>> On 02/10/2011 02:27 AM, Eric Schulte wrote:
Rainer M Krug writes:
> Hi
>
> For one project, I am usinr org to write submit scripte to a cluster
> runing torqu. The impo
21 matches
Mail list logo
