Hi Eric,
Eric Schulte wrote:
> Torsten Anders <torsten.and...@beds.ac.uk> 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 switch on/off "eval never". Hm...
>
> I've just pushed up a patch which adds a new option to the "eval" header
> argument. Setting eval to "non-export" will now allow interactive
> evaluation, but will inhibit code block evaluation during export. This
> should address your need as I understand it.
It certainly is a good addition, but wouldn't it be better to add an
orthogonal argument for the "exports" stuff, that is a second parameter?
I mean: you've added `non-export' which maps to:
- `yes' for interactive evaluation
- `never' for export
I'm sure a guy (or a woman) will ask in a short future for:
- `query' for interactive evaluation
- `never' for export.
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?).
Best regards,
Seb
Footnotes:
[1] Like for results, where we can give up to 3 options:
`:results output scalar raw'
--
Sebastien Vauban
