From: Eric Schulte <firstname.lastname@example.org> To: R.M.Krug@gmail.com Cc: emacs-orgmode <email@example.com> Subject: Re: [babel] [bug] bug in R-specific header argument for graphics driver Date: Mon, 19 Mar 2012 10:48:18 -0400 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <4F67441B.email@example.com> (Rainer M. Krug's message of "Mon, 19 Mar 2012 15:35:07 +0100") Rainer M Krug <firstname.lastname@example.org> writes: > On 19/03/12 15:17, Eric Schulte wrote: >> Hi Rainer, >> >> I see you CC'd me on this email. I personally do not know anything about how the graphics >> header argument to R code blocks works. > > Sorry - I thought it was part of babel, and when I hear "babel", I think "eric knows it"... > It is part of Babel, but Dan Davison is the author of much of the R code, and in general there are increasingly language-specific authors who know more about support particular to a specific language than do I. > > >> I would recommend looking deeper into the behavior using the following tools >> >> - Look at the expanded code block body using org-babel-expand-src-block - Run the code block in >> a session, and then look into the session buffer to see what R code is being generated by >> Babel, then try to debug the R as you would normally - look into the temporary R scripts >> generated during execution, which will live in a directory with a name like /tmp/babel-XXXXXX > > Good idea - I'll look into it and give you feedback. > Great, Thanks, > >> >> If you are able to isolate a bug in Babel then I can help fix that bug in the elisp code. > > Thanks - I still haven't managed to get into (e)lisp... > >> >> Thanks and sorry I can't be of more immediate, > > No problem, > > Cheers, > > Rainer > >> >> Rainer M Krug <email@example.com> writes: >> >>> I did not get any response so far, so I hope that the email did not went out... >>> >>> Rainer >>> >>> >> When giving the header argument :title: the graph is not produced in a file: >> >> * This works Display boxplot of spread of Mff over time for each release strategy :PROPERTIES: >> :results: graphics :file: SpreadOverTime.pdf :width: 4 :height: 8 :pointsize: 8 :END: >> #+begin_src R plot(runif(100)) #+end_src >> >> * This doesn't Display boxplot of spread of Mff over time for each release strategy >> :PROPERTIES: :results: graphics :file: test.pdf :width: 4 :height: 8 :pointsize: 8 :title: >> "test" :END: #+begin_src R plot(runif(100)) #+end_src >> >> Error message: >> >> Error in pdf(file = "test.pdf", width = 4, height = 8, pointsize = 8, : object 'test' not >> found Calls: <Anonymous> -> <Anonymous> -> pdf Execution halted >> >> Cheers, >> >> Rainer >> >> -- Eric Schulte http://cs.unm.edu/~eschulte/
next prev parent reply other threads:[~2012-03-19 14:48 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-19 8:55 Rainer M Krug 2012-03-19 14:17 ` Eric Schulte 2012-03-19 14:35 ` Rainer M Krug 2012-03-19 14:48 ` Eric Schulte [this message] -- strict thread matches above, loose matches on Subject: below -- 2012-03-15 12:24 Rainer M Krug
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 \ --firstname.lastname@example.org \ --email@example.com \ --cc=R.M.Krug@gmail.com \ --firstname.lastname@example.org \ --subject='Re: [babel] [bug] bug in R-specific header argument for graphics driver' \ /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
Code repositories for project(s) associated with this 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).