From: Richard Stanton <stanton@haas.berkeley.edu>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Setting org-export-use-babel to nil causes exporting to ignore :exports header
Date: Thu, 14 Sep 2017 07:42:15 -0700 [thread overview]
Message-ID: <11A8D5FD-2103-43B1-9CCD-27EE5A662AA4@haas.berkeley.edu> (raw)
In-Reply-To: <87wp51l9mg.fsf@nicolasgoaziou.fr>
Thanks, Nicolas. It looks like the default behavior changed at some point but it could have been some while ago...
Sent from my iPad
> On Sep 14, 2017, at 5:58 AM, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
>
> Hello,
>
> Richard Stanton <stanton@haas.berkeley.edu> writes:
>
>> Emacs : GNU Emacs 25.2.1 (x86_64-apple-darwin16.7.0, Carbon Version 157 AppKit 1504.83)
>> of 2017-08-28
>> Package: Org mode version 9.1 (9.1-20-ga4f139-elpa @ /Users/stanton/.emacs.d/elpa/org-20170911/)
>>
>> I typically set org-export-use-babel to nil, to prevent all the code
>> cells being executed on export. However, if this variable is set, org
>> export both code and results for each cell, regardless of the setting of
>> the :exports header option. Withoput this variable being set, exporting
>> correctly obeys the :exports directives in the cell headers.
>
> Here is `org-export-use-babel' docstring:
>
> Switch controlling code evaluation and header processing during
> export. When set to nil no code will be evaluated as part of the
> export process and no header arguments will be obeyed. Users who wish
> to avoid evaluating code on export should use the header argument
> ‘:eval never-export’.
>
> So you need to use ":eval never-export", not that variable.
>
> Regards,
>
> --
> Nicolas Goaziou
prev parent reply other threads:[~2017-09-14 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-13 22:42 Bug: Setting org-export-use-babel to nil causes exporting to ignore :exports header Richard Stanton
2017-09-14 12:58 ` Nicolas Goaziou
2017-09-14 14:42 ` Richard Stanton [this message]
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=11A8D5FD-2103-43B1-9CCD-27EE5A662AA4@haas.berkeley.edu \
--to=stanton@haas.berkeley.edu \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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.