From: John Hendy <jw.hendy@gmail.com>
To: Jack Kamm <jackkamm@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Refresher on including R/ggplot2 output via latex/pdf?
Date: Sun, 27 Oct 2019 23:40:34 -0500 [thread overview]
Message-ID: <CA+M2ft_u=uMSv90hnGnsxt72hnOxDgX9DzwwOs_rTrWr3cYJaw@mail.gmail.com> (raw)
In-Reply-To: <87sgndlcbe.fsf@gmail.com>
On Sun, Oct 27, 2019 at 11:31 PM Jack Kamm <jackkamm@gmail.com> wrote:
>
> Your code block looks fine to me. The typical R code block headers I use is as follows:
Did you try to reproduce my example, by chance?
> :session :results output graphics :file path/to/file.png :exports results :eval never-export
Using this:
-----
#+begin_src R :session :results output graphics :file foo.png :exports
results :eval never-export
library(ggplot2)
df <- data.frame(x=c(1, 2), y=c(2, 4))
p <- ggplot(df, aes(x = x, y = y)) + geom_point()
print(p)
#+end_src
-----
I get an empty #+RESULTS: header, but no inserted file link. The plot
is not in the exported PDF either.
If I make it this:
-----
#+begin_src R :session :results file graphics :file foo.png :exports
results :eval never-export
-----
I get the expected results, and the plot is in the output PDF.
-----
#+RESULTS:
[[file:foo.png]]
-----
> One thing I've noticed, if I have an existing graphics device open, it
> can mess up plots when executing an org-babel cell. Calling dev.off() a
> few times fixes this for me.
>
> Note I pretty much always use R blocks with the :session argument,
> things might be pretty different without it.
I usually use :session as well (and have it in my actual document, but
left it off for this test case). Still, using your header (minus
changing the file path/type) didn't work for me.
Thanks for taking a look,
John
next prev parent reply other threads:[~2019-10-28 4:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 4:16 Refresher on including R/ggplot2 output via latex/pdf? John Hendy
2019-10-28 4:32 ` Jack Kamm
2019-10-28 4:40 ` John Hendy [this message]
2019-10-28 5:03 ` Jack Kamm
2019-10-28 5:13 ` John Hendy
2019-10-28 6:15 ` Jack Kamm
2019-10-28 7:43 ` John Hendy
2019-10-28 16:21 ` Berry, Charles
2019-10-28 16:30 ` John Hendy
2019-10-28 17:46 ` Jack Kamm
2019-10-29 14:39 ` John Hendy
2019-10-29 14:50 ` Jack Kamm
2019-10-29 15:13 ` John Hendy
2019-11-30 19:21 ` Jack Kamm
2019-10-28 8:21 ` Dominique Dumont
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='CA+M2ft_u=uMSv90hnGnsxt72hnOxDgX9DzwwOs_rTrWr3cYJaw@mail.gmail.com' \
--to=jw.hendy@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jackkamm@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).