From: "Charles C. Berry" <ccberry@ucsd.edu>
To: "\"Martin Gürtler\"" <Martin.Guertler@gmx.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: src blocks: code is /always/ exported
Date: Thu, 29 Dec 2016 09:07:40 -0800 [thread overview]
Message-ID: <alpine.OSX.2.20.1612290859220.668@charles-berrys-macbook.local> (raw)
In-Reply-To: <trinity-c01c40ec-7a81-471e-b193-5fd0120f31cc-1483023218518@3capp-gmx-bs24>
[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]
On Thu, 29 Dec 2016, "Martin Gürtler" wrote:
> Dear list,
> I am exporting the following org mode file:
> ----8<--------------------
> * doc
> #+BEGIN_SRC shell :exports none
> ls |wc
> #+END_SRC
> #+RESULTS:
> : 20 20 199
> ----8<--------------------
> I'd expect org mode to honour the :exports none header argument and
> create a document that contains only the result.
> However, the exported document contains both, code and results.
> This seems to be independent of the type of SRC and independent of the
> export type (I tried dot and shell for odt, latex and beamer exports).
> How can I get rid of the src code in the exported document?
What does C-h v org-export-use-babel RET say?
If the result is not `t' that is the problem, and somewhere in your setup
you have set that variable (or its predecessor org-export-babel-evaluate)
to nil or something other than `t'.
If this is the problem, set org-export-use-babel to `t'. You might
also note the advice in the docstring:
"Users who wish to avoid evaluating code on export should use the header
argument ‘:eval never-export’."
HTH,
Chuck
next prev parent reply other threads:[~2016-12-29 17:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 14:53 src blocks: code is /always/ exported "Martin Gürtler"
2016-12-29 17:07 ` Charles C. Berry [this message]
2016-12-29 18:45 ` Martin Gürtler
2016-12-29 20:05 ` Lars E. Pettersson
2016-12-29 20:12 ` 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
* 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.1612290859220.668@charles-berrys-macbook.local \
--to=ccberry@ucsd.edu \
--cc=Martin.Guertler@gmx.de \
--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 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.