Dear Eric,
Sorry for the noise, it works fine.
> see the manual for valid values for the eval header argument.
I actually did, but only the online version so far. Of course, for such changes
I had to check the doc sources...
Anyway, thanks a lot!!
Best wishes,
Torsten
On 28 Nov 2011, at 0
Hi Torsten,
Change "non-export" to "no-export", see the manual for valid values for
the eval header argument.
Best -- Eric
Torsten Anders writes:
> Dear Eric,
>
> Apologies for my late response (too much teaching and admin in this new job
> :-P). Thanks a lot again for kingly adding the "eval
Dear Eric,
Apologies for my late response (too much teaching and admin in this new job
:-P). Thanks a lot again for kingly adding the "eval" header
argument "non-export". From what I understand in your message this would be
exactly what I was looking for (allow interactive
evaluation, but inhibi
Bernt Hansen writes:
> Eric Schulte writes:
>
>>>
>>> Hence, maybe we should be able to set 2 possible behaviors[1] for the
>>>`eval'
>>> parameter:
>>>
>>> - one for the interactive mode (yes/query/no), and
>>> - one for the export mode (yes/no, and maybe query as well?).
>>>
>>
>> Agreed,
>>
>
Eric Schulte writes:
>>
>> Hence, maybe we should be able to set 2 possible behaviors[1] for the
>>`eval'
>> parameter:
>>
>> - one for the interactive mode (yes/query/no), and
>> - one for the export mode (yes/no, and maybe query as well?).
>>
>
> Agreed,
>
> The eval header argument now support
>
> Hence, maybe we should be able to set 2 possible behaviors[1] for the
>`eval'
> parameter:
>
> - one for the interactive mode (yes/query/no), and
> - one for the export mode (yes/no, and maybe query as well?).
>
Agreed,
The eval header argument now supports the following four options
(updated
Hi Eric,
Eric Schulte wrote:
> Torsten Anders writes:
>> Thanks a lot for your kind replies. However, this is not yet quite what I am
>> after.
>>
>> I want to be able to manually execute each code block, but not
>> automatically whenever the whole document is rendered. So, I would
>> always swi
Hi Torsten,
Torsten Anders writes:
> Dear Sebastien and Eric,
>
> Thanks a lot for your kind replies. However, this is not yet quite what I am
> after.
>
> I want to be able to manually execute each code block, but not
> automatically whenever the whole document is rendered. So, I would
> alway
Dear Sebastien and Eric,
Thanks a lot for your kind replies. However, this is not yet quite what I am
after.
I want to be able to manually execute each code block, but not automatically
whenever the whole document is rendered. So, I would always switch on/off "eval
never". Hm...
I will try o
"Sebastien Vauban" writes:
> Hi Torsten,
>
> Torsten Anders wrote:
>> Dear Org-Babel developers,
>>
>> When I am exporting an *.org buffer to, say, HTML or PDF (via Latex) the
>> code blocks of at least some languages are executed during the export
>> process. (Has this always been like that, I n
Hi Torsten,
Torsten Anders wrote:
> Dear Org-Babel developers,
>
> When I am exporting an *.org buffer to, say, HTML or PDF (via Latex) the
> code blocks of at least some languages are executed during the export
> process. (Has this always been like that, I noticed this for the first
> time?)
>
>
Dear Org-Babel developers,
When I am exporting an *.org buffer to, say, HTML or PDF (via Latex) the code
blocks of at least some languages are executed during the export process. (Has
this always been like that, I noticed this for the first time?)
I would like to switch that off completely. I
12 matches
Mail list logo
