On Mon, 9 Feb 2015, Sebastien Vauban wrote:
Charles C. Berry wrote:
On Fri, 23 Jan 2015, Sebastien Vauban wrote:
Charles C. Berry wrote:
Sebastien Vauban wrote:
In a long document, I must have :eval no at file level, as this
is the common setting for most code blocks. However, how do I
Charles C. Berry wrote:
On Fri, 23 Jan 2015, Sebastien Vauban wrote:
Charles C. Berry wrote:
Sebastien Vauban wrote:
In a long document, I must have :eval no at file level, as this
is the common setting for most code blocks. However, how do I unset
that for some call lines.
I don't get why
On Fri, 23 Jan 2015, Sebastien Vauban wrote:
Charles C. Berry wrote:
Sebastien Vauban wrote:
In a long document, I must have :eval no at file level, as this is
the common setting for most code blocks. However, how do I unset that
for some call lines.
[snip]
I don't get why one has to add
Charles C. Berry wrote:
Sebastien Vauban wrote:
In a long document, I must have :eval no at file level, as this is
the common setting for most code blocks. However, how do I unset that
for some call lines.
See (info (org) Evaluating code blocks)
Note what it says about 'inside' and
Hello,
May I bump up this thread?
Sebastien Vauban wrote:
In a long document, I must have :eval no at file level, as this is the
common setting for most code blocks. However, how do I unset that for
some call lines.
Export this ECM (to HTML, for example) and see for yourself that it does
On Thu, 22 Jan 2015, Sebastien Vauban wrote:
Hello,
May I bump up this thread?
Sebastien Vauban wrote:
In a long document, I must have :eval no at file level, as this is the
common setting for most code blocks. However, how do I unset that for
some call lines.
See (info (org) Evaluating
Hello,
In a long document, I must have :eval no at file level, as this is the
common setting for most code blocks. However, how do I unset that for
some call lines.
Export this ECM (to HTML, for example) and see for yourself that it does
not seem evident...
--8---cut
