From: "Charles C. Berry" <ccberry@ucsd.edu>
To: Thomas Alexander Gerds <tag@biostat.ku.dk>
Cc: emacs-orgmode@gnu.org, istazahn@gmail.com
Subject: Re: export of src block ignores :results
Date: Sat, 1 Oct 2016 09:32:48 -0700 [thread overview]
Message-ID: <alpine.OSX.2.20.1610010900370.582@charles-berrys-macbook.local> (raw)
In-Reply-To: <878tu8oc32.fsf@biostat.ku.dk>
On Fri, 30 Sep 2016, Thomas Alexander Gerds wrote:
>
> right, this is what changed and setting :eval never-export on a each
> block solves the problem. however, the new way breaks all my existing
> org-code.
I don't follow this. What exactly is broken?
You know all the options for setting header args, right? System-wide,
buffer-wide, etc. For buffer-wide setting, one line is all it takes:
: #+PROPERTY: header-args :eval never-export
(and remember to C-c C-c on that line whenever you insert/edit it)
>
> is there a reason why the header args have to be ignored when
> org-export-babel-evaluate is nil? or asking more directly: would it be
> possible to have another option, e.g.,
>
> (setq org-export-babel-evaluate 'never-eval-obey-header-args)
>
But that is what :eval never-export does.
> such that the export process does never evaluate src code but header
> arguments are always obeyed?
>
Possible, yes. But since it adds no new capability and makes the babel
code more involved, there isn't the motivtion to do it.
Chuck
next prev parent reply other threads:[~2016-10-01 16:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 6:42 export of src block ignores :results Thomas Alexander Gerds
2016-09-29 16:25 ` Charles C. Berry
2016-09-29 19:53 ` Thomas Alexander Gerds
2016-09-29 21:02 ` Charles C. Berry
2016-09-30 3:39 ` Charles C. Berry
2016-09-30 5:06 ` Thomas Alexander Gerds
2016-09-30 17:05 ` Charles C. Berry
2016-10-01 5:46 ` Thomas Alexander Gerds
2016-10-01 16:32 ` Charles C. Berry [this message]
2016-10-02 11:08 ` Thomas Alexander Gerds
2016-10-01 8:37 ` Nicolas Goaziou
-- strict thread matches above, loose matches on Subject: below --
2016-09-29 6:43 Thomas Alexander Gerds
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.OSX.2.20.1610010900370.582@charles-berrys-macbook.local \
--to=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=istazahn@gmail.com \
--cc=tag@biostat.ku.dk \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.