From: John Hendy <jw.hendy@gmail.com>
To: "Berry, Charles" <ccberry@ucsd.edu>
Cc: Jack Kamm <jackkamm@gmail.com>, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Refresher on including R/ggplot2 output via latex/pdf?
Date: Mon, 28 Oct 2019 11:30:57 -0500 [thread overview]
Message-ID: <CA+M2ft8nh6iBgfU8CHW2KR1oNjC1DbZ-JfGV7eYE90DEf-T6bw@mail.gmail.com> (raw)
In-Reply-To: <08172A54-EF30-43BB-84E2-C573C7EA14B2@ucsd.edu>
On Mon, Oct 28, 2019 at 11:22 AM Berry, Charles <ccberry@ucsd.edu> wrote:
>
>
>
> > On Oct 28, 2019, at 12:43 AM, John Hendy <jw.hendy@gmail.com> wrote:
> >
> > On Mon, Oct 28, 2019 at 1:14 AM Jack Kamm <jackkamm@gmail.com> wrote:
> >>
> >>> This is with emacs -Q and loading the minimal config from the initial
> >>> email. Any ideas on where I might look next?
> >>
> >> Sorry, I don't have many ideas here. Have you checked that ggplot works fine in a regular R session?
> >
> > Indeed, it does. And as mentioned, if I used :results file graphics,
> > everything works. It's able to plot and write to file... the magic
> > just isn't happening with :results output graphics for some reason.
> >
> >
>
>
> To wit:
>
> commit 5c55d3a53c982563c0409e342b8940009e1409f2
> Author: Nicolas Goaziou <mail@nicolasgoaziou.fr>
> Date: Sat Aug 24 00:04:06 2019 +0200
>
> manual: Remove erroneous footnote about :file header argument
>
> * doc/org-manual.org (Type): :file header argument no longer
> implies :results file.
>
> commit 26ed66b23335eb389f1f2859e409f46f66279e15
> Author: Nicolas Goaziou <mail@nicolasgoaziou.fr>
> Date: Sat Oct 6 08:56:05 2018 +0200
>
> ob: :file and :file-ext no longer imply :results file
>
> * lisp/ob-core.el (org-babel-execute-src-block): ":results file" must
> be specified in order to return a file.
> (org-babel-merge-params): :file and :file-ext no longer imply :results
> file.
> * testing/lisp/test-ob.el (test-ob/indented-cached-org-bracket-link):
> (test-ob/result-file-link-type-header-argument):
> (test-ob/result-graphics-link-type-header-argument): Update tests.
>
> Deducing the results from some other arguments is not obvious.
> Moreover, it prevents users from setting, e.g., :file-ext, in a node
> property, as every block would then create a file.
>
> Reported-by: Alex Fenton <alex@pressure.to>
> <http://lists.gnu.org/r/emacs-orgmode/2018-05/msg00469.html>
Ok, this is promising. How do we explain the results, though?
I had this issue in the original post on:
Org mode version 9.2.4 (release_9.2.4-381-g226363 @
/home/jwhendy/.elisp/org/lisp/)
commit 226363482305d596bfb91e50246eb82d78689795
Author: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Date: Sat Jun 22 09:33:33 2019 +0200
Then I updated and still got the same behavior on:
Org mode version 9.2.6 (release_9.2.6-559-ga01a8f @
/home/jwhendy/.elisp/org/lisp/)
commit a01a8f55d8bf259ebecc050c162c48e29da13bee (HEAD -> master,
origin/master, origin/HEAD)
Merge: 58ceff522 9c611fd8a
Author: Kyle Meyer <kyle@kyleam.com>
Date: Sun Oct 27 15:55:30 2019 -0400
My questions:
1) why didn't my example work for me on the commit from Jun 22 (< Aug or Oct)
2) why does this [still] work for Jack? (Jack, what's M-x org-version for you?)
3) optionally: can you reproduce the issue?
Thanks,
John
> HTH,
>
> Chuck
>
>
>
next prev parent reply other threads:[~2019-10-28 16:33 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
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 [this message]
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+M2ft8nh6iBgfU8CHW2KR1oNjC1DbZ-JfGV7eYE90DEf-T6bw@mail.gmail.com \
--to=jw.hendy@gmail.com \
--cc=ccberry@ucsd.edu \
--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).