From: Colin Baxter <m43cap@yandex.com>
To: Derek Feichtinger <derek.feichtinger@psi.ch>
Cc: emacs-orgmode@gnu.org, "Charles C. Berry" <ccberry@ucsd.edu>
Subject: Re: org-export-babel-evaluate=nil ignores ":exports results" setting - this has changed
Date: Wed, 22 Feb 2017 18:56:09 +0000 [thread overview]
Message-ID: <87mvdekqba.fsf@yandex.com> (raw)
In-Reply-To: <ac114f9b-97a6-f245-d95a-a817b0e69824@psi.ch> (Derek Feichtinger's message of "Wed, 22 Feb 2017 16:45:26 +0100")
On Wed, Feb 22 2017, Derek Feichtinger wrote:
Dear Derek,
> Hi Colin
>
> On 22.02.2017 16:27, Colin Baxter wrote:
>> Hi.
>>
>> On Tue, Feb 21 2017, Charles C. Berry wrote:
>>
>>> On Mon, 20 Feb 2017, Derek Feichtinger wrote:
>>>
--------- snip ---------
> Based on the documentation one can set the header arguments system wide
> using these variables:
>
> org-babel-default-header-args (for all)
> org-babel-default-header-args:<lang> (language specific)
>
> File wide using PROPERTY:
>
> #+PROPERTY: header-args :eval never-export
>
> Org heading wide using a local property setting:
> * sample header
> :PROPERTIES:
> :header-args: :eval never-export
> :END:
>
> The last two ways I tested. So, in the end, with some changes to most of
> my files I can get the same behavior again, which is good.
>
> It's a matter of taste or use case whether to define the default
> behavior to eval on export. I would have made the case the eval on
> export is the more rare use case. I almost never have this, except for
> certain kinds of reports, e.g. if you want to gather the state of a
> server with a number of prepared queries in the org file. For me, most
> org files are like a number of measurements taken at a certain point in
> time, and I want to conserve the output of the evaluation exactly like
> it was. E.g. when working at speeding up code, I very much like to do
> the whole thing inside of an org file where I document the speed
> measurements, my changes to code and what the effect was. So, more like
> some kind of interactive lab journal.
>
> But as I said, it is a matter of taste, and I am happy that I can get
> the original functionality without too much effort.
>
> Best regards,
> Derek
--------------- snip ---------
Thank you, I really appreciate this information. You have saved me a
couple of hours work. I'll probably end up setting
org-babel-default-header-args as a local variable.
Thanks again.
Best wishes.
next prev parent reply other threads:[~2017-02-22 18:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 22:02 org-export-babel-evaluate=nil ignores ":exports results" setting - this has changed Derek Feichtinger
2017-02-20 23:54 ` Charles C. Berry
2017-02-21 6:05 ` Derek Feichtinger
2017-02-21 16:37 ` Charles C. Berry
2017-02-22 15:27 ` Colin Baxter
2017-02-22 15:45 ` Derek Feichtinger
2017-02-22 18:56 ` Colin Baxter [this message]
2017-02-21 10:51 ` Aaron Ecay
2017-02-21 16:40 ` Charles C. Berry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mvdekqba.fsf@yandex.com \
--to=m43cap@yandex.com \
--cc=ccberry@ucsd.edu \
--cc=derek.feichtinger@psi.ch \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).