Correction:
#+PROPERTY: header-args :eval never-export
is the right incantation below.
Chuck
On Tue, 24 May 2016, Charles C. Berry wrote:
On Tue, 24 May 2016, Ista Zahn wrote:
On Tue, May 24, 2016 at 6:17 AM, Andreas Kiermeier
wrote:
I second that.
I like exporting everything to LaTeX w
On Tue, 24 May 2016, Ista Zahn wrote:
On Tue, May 24, 2016 at 6:17 AM, Andreas Kiermeier
wrote:
I second that.
I like exporting everything to LaTeX without having to re-run all the code,
which in many cases can add considerable time.
Which you can still do, I guess by
(setq org-babel-defaul
On Tuesday, May 24, 2016, Ista Zahn wrote:
> On Tue, May 24, 2016 at 6:17 AM, Andreas Kiermeier
> > wrote:
>
> It this change is not going to be reversed than the doc string for
> org-export-babel-evaluate needs to be updated, and something should go
> in the NEWS file warning people (like me) wh
On Tue, May 24, 2016 at 6:17 AM, Andreas Kiermeier
wrote:
> I second that.
> I like exporting everything to LaTeX without having to re-run all the code,
> which in many cases can add considerable time.
Which you can still do, I guess by
(setq org-babel-default-header-args
(cons '(:eval . "
I second that.
I like exporting everything to LaTeX without having to re-run all the code,
which in many cases can add considerable time.
Cheers,
Andreas
On 24 May 2016 at 11:04, Grant Rettke wrote:
> On Sun, May 22, 2016 at 4:52 PM, Charles C. Berry
> wrote:
> > TL;DR: Org babel headers give e
On Sun, May 22, 2016 at 4:52 PM, Charles C. Berry wrote:
> TL;DR: Org babel headers give excellent control over what gets run,
> when it gets run, and how. Users should use them.
Definitely!
> Don't reset `org-export-babel-evaluate'.
Why not?
It can be nice to disable org-export-babel-evaluate
On Mon, 23 May 2016, Nick Dokos wrote:
"Charles C. Berry" writes:
TL;DR: Org babel headers give excellent control over what gets run,
when it gets run, and how. Users should use them. Don't reset
`org-export-babel-evaluate'.
...
[snip]
Frankly, I do not see why users would want to mess
On Mon, May 23, 2016 at 1:27 PM, Nick Dokos wrote:
> "Charles C. Berry" writes:
[snip]
>
>> If there is a use case for a capability that is not well supported by
>> existing headers it would be good to have an example.
>>
>
> There's the use case that John describes: I've evaluated everything,
"Charles C. Berry" writes:
> TL;DR: Org babel headers give excellent control over what gets run,
> when it gets run, and how. Users should use them. Don't reset
> `org-export-babel-evaluate'.
>
> ...
>
>> I think one of the main points of confusion in this thread still has
>> to do with why o-e-b
John and Nick,
Comments in line below.
TL;DR: Org babel headers give excellent control over what gets run,
when it gets run, and how. Users should use them. Don't reset
`org-export-babel-evaluate'.
Chuck
On Sun, 22 May 2016, John Hendy wrote:
On Fri, May 20, 2016 at 4:20 PM, Charles C. Berr
On Fri, May 20, 2016 at 4:20 PM, Charles C. Berry wrote:
> On Fri, 20 May 2016, Nick Dokos wrote:
>
>> Ken Mankoff writes:
>>
> [deleted discussion of `org-export-babel-evaluate' settings]
>
>>
>> With ":exports results" and o-e-b-e set to nil, I get no evaluation on
>> export, but I get both co
"Charles C. Berry" writes:
> On Fri, 20 May 2016, Nick Dokos wrote:
>
>> Ken Mankoff writes:
>>
> [deleted discussion of `org-export-babel-evaluate' settings]
>
>>
>> With ":exports results" and o-e-b-e set to nil, I get no evaluation on
>> export, but I get both code and results in the output.
On 2016-05-20 at 14:46, Nick Dokos wrote:
> Are you getting an evaluation on export? I don't get that with o-e-b-e
> set to nil.
No I was not, but things were still exporting, which was confusing. I agree,
seems like a bug.
> ... the fact that I get both code and results even if I specify
> "
On Fri, 20 May 2016, Nick Dokos wrote:
Ken Mankoff writes:
[deleted discussion of `org-export-babel-evaluate' settings]
With ":exports results" and o-e-b-e set to nil, I get no evaluation on
export, but I get both code and results in the output.
There may have been a misunderstanding, b
Ken Mankoff writes:
> On 2016-05-20 at 13:11, Eric S Fraga wrote:
>> On Friday, 20 May 2016 at 17:06, Ken Mankoff wrote:
>> So, if I understand correctly, you have org-export-babel-evaluate set
>> to nil?
>
> yes.
>
Are you getting an evaluation on export? I don't get that with o-e-b-e
set to n
On Friday, 20 May 2016 at 16:45, Ken Mankoff wrote:
> Eric: You're running something newer (by date) than the commit which
> changed the behavior, which was:
>
> ec615b1 - Fix `org-export-babel-evaluate' handling (2016-04-28)
>
> But with all the branches in git, I don't know if you have that commi
Nicolas Goaziou added to To: field, because he committed the change.
Question: Why does "org-export-babel-evaluate" change what is exported?
Shouldn't it just change what is evaluated at export time? That is what the doc
string implies. A recent commit changed this behavior.
-k.
On 2016-05-
On 2016-05-20 at 13:11, Eric S Fraga wrote:
> On Friday, 20 May 2016 at 17:06, Ken Mankoff wrote:
> So, if I understand correctly, you have org-export-babel-evaluate set
> to nil?
yes.
> If I set that, I no longer get asked whether I want anything evaluated
> but the (existing) results do get e
On Fri, May 20, 2016 at 11:45 AM, Ken Mankoff wrote:
>
> Eric: You're running something newer (by date) than the commit which changed
> the behavior, which was:
>
> ec615b1 - Fix `org-export-babel-evaluate' handling (2016-04-28)
>
> But with all the branches in git, I don't know if you have that
On Fri, May 20, 2016 at 12:11 PM, Eric S Fraga wrote:
> On Friday, 20 May 2016 at 17:06, Ken Mankoff wrote:
>
> [...]
>
>> Thanks for clarifying your workflow. That seems to work for a small
>> example. But what would you do if you had a manuscript with 100 code
>> blocks in it? And in general you
On Friday, 20 May 2016 at 17:06, Ken Mankoff wrote:
[...]
> Thanks for clarifying your workflow. That seems to work for a small
> example. But what would you do if you had a manuscript with 100 code
> blocks in it? And in general you're exporting it a lot without
> changing anything in code, just
Hi Eric,
On 2016-05-20 at 12:59, Eric S Fraga wrote:
> When I export, org asks whether to evaluate the code block and I
> respond with no. The existing results block is therefore exported but
> not changed. If I say yes, a new results block is generated and
> exported (and I can tell because it i
Eric: You're running something newer (by date) than the commit which changed
the behavior, which was:
ec615b1 - Fix `org-export-babel-evaluate' handling (2016-04-28)
But with all the branches in git, I don't know if you have that commit or not.
Anyway, I'm not sure why it works for you. It doe
On Friday, 20 May 2016 at 15:57, Ken Mankoff wrote:
> Hi List,
>
> I'm repeating a question here from a recent bug report because I have
> a feeling official-looking bug reports might get read less than normal
> questions. Sorry for the re-post.
>
> As of an Org git commit a few weeks ago, Org expo
On Fri, May 20, 2016 at 10:57 AM, Ken Mankoff wrote:
> Hi List,
>
> I'm repeating a question here from a recent bug report because I have a
> feeling official-looking bug reports might get read less than normal
> questions. Sorry for the re-post.
>
> As of an Org git commit a few weeks ago, Org
Hi List,
I'm repeating a question here from a recent bug report because I have a feeling
official-looking bug reports might get read less than normal questions. Sorry
for the re-post.
As of an Org git commit a few weeks ago, Org exporting (and therefore Org) has
become basically unusable for m
26 matches
Mail list logo
