From mboxrd@z Thu Jan 1 00:00:00 1970 From: tsd@tsdye.com (Thomas S. Dye) Subject: Re: Selective export of Babel code blocks Date: Mon, 18 Jun 2012 07:11:29 -1000 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([208.118.235.92]:55439) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SgfUU-0000Bn-Sd for emacs-orgmode@gnu.org; Mon, 18 Jun 2012 13:11:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SgfUM-0004fp-0p for emacs-orgmode@gnu.org; Mon, 18 Jun 2012 13:11:50 -0400 Received: from oproxy6-pub.bluehost.com ([67.222.54.6]:36535) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1SgfUL-0004f1-NX for emacs-orgmode@gnu.org; Mon, 18 Jun 2012 13:11:41 -0400 In-Reply-To: (John Hendy's message of "Mon, 18 Jun 2012 09:53:57 -0500") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: John Hendy Cc: emacs-orgmode John Hendy writes: > I recently started a paper using Babel in a more full-functioned way > to display both R code as well as output. Previously I've just used > the convenience of headings and src blocks to create R plots and have > the code stored nicely for future reference. I'm exporting via LaTeX > to create something to promote R and why it's awesome in conjunction > with org-mode at work, which is a Minitab environment. Thus, I'd like > to include actual R code to familiarize others. On with the problem. > I'm also using tikzDevice. Thus, my paper so far is about like so: > > ---------- > * Plotting this vs. that > > Not we'll plot this vs. that. Here's the R code: > > #+begin_src R :exports none > tikzDevice("file.tex", width=6, height=4, standAlone=T) > #+end_src > > #+begin_src R :exports both > data <- read.csv("file.csv", header=T) > sub <- subset(data, output > 5) > ggplot(sub, aes(x=x, y=y)) + geom_point() > #+end_src > > #+begin_src R :exports none > dev.off() > tools::texi2pdf("file.tex") > #+end_src > ---------- > > Anyway, something like this. This isn't a huge poroblem... I'm > generating a lot of the same type of scatterplot just using different > variables, so I can copy and yank the blocks and just change > variable/file names. Doing this got me to thinking how it would be > quite neat to run code in a block but mark it to be omitted from > export for these kind of "setup" lines that are necessary for the > desired graphs but unnecessary for your reader to see over and over > again. > > Thoughts? I'm quite a novice and very possibly missed something that > can already do this. > > > Thanks! > John > > Hi John, One way to do this might be to name the source code block and then use an #+CALL: line. #+name: clean-up #+begin_src R :exports code dev.off() tools::texi2pdf("file.tex") #+end_src .... #+CALL: clean-up() :exports none This way, the original code block will be exported and subsequent calls should not be. hth, Tom -- Thomas S. Dye http://www.tsdye.com