From: Thomas Alexander Gerds <tag@biostat.ku.dk>
To: "Charles C. Berry" <ccberry@ucsd.edu>
Cc: emacs-orgmode@gnu.org, istazahn@gmail.com
Subject: Re: export of src block ignores :results
Date: Sat, 01 Oct 2016 07:46:57 +0200 [thread overview]
Message-ID: <878tu8oc32.fsf@biostat.ku.dk> (raw)
In-Reply-To: <alpine.OSX.2.20.1609300946300.581@charles-berrys-macbook.local> (Charles C. Berry's message of "Fri, 30 Sep 2016 10:05:59 -0700")
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.
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)
such that the export process does never evaluate src code but header
arguments are always obeyed?
actually, my org-life improved alot when I found Ista Zahn's (cc) remark
in the org-mode mailing list about setting org-export-babel-evaluate to
nil. here is the quote:
,----Fri, 21 Aug 2015 Re: [O] "user-error: No language for src block ...
| |
| Unless you've restored sanity by setting org-export-babel-evaluate to |
| nil. Personally I think this is not a good default. Source block |
| evaluation and export are distinct actions, and I don't see why they |
| should be linked by default. |
| |
| https://lists.gnu.org/archive/html/emacs-orgmode/2015-08/msg00940.html |
`----
to me personally, the fact that one can separate the export process from
the source block evaluation in org-mode is one of the great advantages
over R-studio's markdown.
Thomas
"Charles C. Berry" <ccberry@ucsd.edu> writes:
> On Thu, 29 Sep 2016, Thomas Alexander Gerds wrote:
>
>>
> [deleted]
>
> Follow the advice in the docstring for
> `org-export-babel-evaluate'. Use `:eval never-export'. Set
> org-export-babel-evaluate to t.
>
> Chuck
>
>
--
sent from nil
next prev parent reply other threads:[~2016-10-01 5:47 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 [this message]
2016-10-01 16:32 ` Charles C. Berry
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
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=878tu8oc32.fsf@biostat.ku.dk \
--to=tag@biostat.ku.dk \
--cc=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=istazahn@gmail.com \
/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).