emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Eric Schulte" <schulte.eric@gmail.com>
To: Neil Hepburn <nhepburn@ualberta.ca>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: odd org-babel R behaviour
Date: Fri, 30 Jul 2010 16:33:53 -0600	[thread overview]
Message-ID: <87r5ik1twu.fsf@gmail.com> (raw)
In-Reply-To: <A4EECCE0-D963-4C3A-A2DE-B132F4FDD536@ualberta.ca> (Neil Hepburn's message of "Fri, 30 Jul 2010 16:20:20 -0600")

Hi Neil,

It sounds like you have blocks of R code which are configured such that
their results are not exported.  You could try setting the :exports
header argument [1] to either "results" or "both" on the block, subtree,
or buffer, language, or system level [2].

Best -- Eric

Neil Hepburn <nhepburn@ualberta.ca> writes:

> After recently upgrading to the most recent org-mode, org-babel R and org-export have shown some rather peculiar behavior. After processing some R code, the results are printed out below the code block with 
>
> #+results:
> #+begin_example
> blah blah blah (at least that's what I suspect reviewers at the last journal I submitted to called the output)
> #+end_example
>
> Now, when I go to export my org file to pdf, the R-output does not appear. However, if I go through and either delete the #+results: line or put a blank line between it and #+begin_example, the export works fine and the output from R appears. The same is true if I export to HTML. 
>
> Now that I know the fix, the problem is easy enough to deal with as I go through a batch of experiments.
>
> -Neil
>
>
>
> =============================================
> Neil Hepburn, Economics Instructor
> Department of Social Sciences, Augustana Faculty
> University of Alberta
> 4901-46 Avenue
> Camrose, Alberta  T4V 2R3
>
> Phone (780) 679-1588
> email nhepburn@ualberta.ca
>
> No trees were harmed in creating this message. (However, millions of electrons were terribly disturbed.)
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Footnotes: 
[1]  http://orgmode.org/manual/exports.html#exports

[2]  http://orgmode.org/manual/Using-header-arguments.html#Using-header-arguments

      reply	other threads:[~2010-07-30 22:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-30 22:20 odd org-babel R behaviour Neil Hepburn
2010-07-30 22:33 ` Eric Schulte [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

  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=87r5ik1twu.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=nhepburn@ualberta.ca \
    /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).