emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alan Lue <alan.lue@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Code Block Headers Appear in Export
Date: Sun, 30 Sep 2012 22:52:24 -0700	[thread overview]
Message-ID: <87zk46hh7r.fsf@rye.gateway.2wire.net> (raw)
In-Reply-To: <87wqzc4fwr.fsf@rye.gateway.2wire.net> (Alan Lue's message of "Sat, 29 Sep 2012 15:34:28 -0700")

Following up.

Does anyone else see this behavior? Headers always appear in the export
whenever my document includes a code block with a separate `#+HEADERS:'

Alan Lue <alan.lue@gmail.com> writes:

> I find that code block header arguments specified with `#+HEADERS:'
> consistently appear in the exported document. For example, exporting the
> following document to PDF or HTML will include the "exports" header in
> the output:
> * Manifestation of Problem
>   Look, our headers appear in the export:
>   #+headers: :exports both
>   #+BEGIN_SRC R :results output
>     sd(rnorm(50))
>   #+END_SRC
> How does one suppress the export of header arguments? For reference, I'm
> using Org-mode version 7.9.1.

  reply	other threads:[~2012-10-01  5:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-29 22:34 Code Block Headers Appear in Export Alan Lue
2012-10-01  5:52 ` Alan Lue [this message]
2012-10-01  7:57 ` Sebastien Vauban
2012-10-01  8:02 ` Sebastien Vauban

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:

  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=87zk46hh7r.fsf@rye.gateway.2wire.net \
    --to=alan.lue@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).