Re: Refresher on including R/ggplot2 output via latex/pdf?

[John Hendy <jw.hendy@gmail.com>]

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