From: "Berry, Charles" <ccberry@ucsd.edu>
To: Ken Mankoff <mankoff@gmail.com>
Cc: emacs-org <emacs-orgmode@gnu.org>
Subject: Re: Painfully Slow Export
Date: Tue, 12 Jun 2018 15:51:16 +0000 [thread overview]
Message-ID: <73844D54-30A4-48CB-8303-6DA3C932A444@ucsd.edu> (raw)
In-Reply-To: <m2sh5sp0ig.fsf@gmail.com>
> On Jun 12, 2018, at 7:01 AM, Ken Mankoff <mankoff@gmail.com> wrote:
>
> I'm trying to export a file to LaTeX. It takes about one minute. The
> file is 12000 lines long and has 200 code blocks. I have set:
>
> #+PROPERTY: header-args :eval never-export
>
That is the right idiom. Of course, you have to refresh the local setup after typing that (C-c C-c with point in the PROPERTY line) or it will have no effect until you save and re-open the file.
It is good to check that you have refreshed and that there are no typos or hidden chars in the line, so go to a src block and type
C-c C-v C-i
and verify that you see something like this
,----
| Lang: R
| Properties:
| :header-args :eval never-export
| :header-args:R nil
| Header Arguments:
| :cache no
| :eval never-export
| :exports code
| :hlines no
| :noweb no
| :results replace
| :session none
| :tangle no
`----
You should see both the :header-args line as you typed it and the :eval line showing never-export.
> which means, I think, no babel blocks should evaluate.
>
> (setq org-export-use-babel t) seems to be the culprit.
Leave it set to `t'.
Chuck
next prev parent reply other threads:[~2018-06-12 15:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 14:01 Painfully Slow Export Ken Mankoff
2018-06-12 15:09 ` Chris
2018-06-12 19:41 ` Ken Mankoff
2018-06-12 15:51 ` Berry, Charles [this message]
2018-06-12 19:41 ` Ken Mankoff
2018-06-12 21:07 ` Berry, Charles
2018-06-12 21:15 ` Ken Mankoff
2018-06-12 21:30 ` Ken Mankoff
2018-06-12 22:07 ` Berry, Charles
2018-06-13 5:32 ` Ken Mankoff
2018-06-13 17:55 ` Berry, Charles
2018-06-13 18:32 ` Ken Mankoff
2018-06-14 4:42 ` Ken Mankoff
2018-06-14 18:34 ` BUG? WAS: " Berry, Charles
2018-06-23 21:06 ` Nicolas Goaziou
2018-06-24 1:53 ` Berry, Charles
2018-06-25 13:55 ` Ken Mankoff
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=73844D54-30A4-48CB-8303-6DA3C932A444@ucsd.edu \
--to=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=mankoff@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).