[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] Proposal/request for input: slidify export for html slides

From: Charles Berry
Subject: Re: [O] Proposal/request for input: slidify export for html slides
Date: Mon, 10 Feb 2014 04:16:16 +0000 (UTC)
User-agent: Loom/3.14 (http://gmane.org/)

John Hendy <jw.hendy <at> gmail.com> writes:

> On Sat, Feb 8, 2014 at 11:18 AM, Charles Berry <ccberry <at> ucsd.edu> wrote:

> > But there is some effort and overhead involved, so only the most
> > useful (IMO) have been mapped. Right now, `:noweb yes' will expand the
> > reference(s) in place before export, and `:exports none' will not export
> > the block. Maybe one day ...
> Understood, and no worries. I'm making progress. When you say "expand
> references," I'm not sure I follow what that means. References =
> references to variables? So something like :var something=something?

'References' refers to noweb references. See


> > More a matter of what my workflow is (so the issue doesn't arise). I use
> > the cache=TRUE chunk option on the knitr side to save the results of 
> > long
> > running computations. When I start work, I execute a src block that 
> > loads
> > knitr and knits the *.Rnw (or *.Rmd, etc), which has the side effect of
> > loading the cached objects. Then I edit the *.org document. If I am
> > working on R code, I run the code interactively either from the src edit
> > buffer or I C-c C-c the src block. Its handy to leave the results in the
> > *.org buffer for reference - they get stripped on export. Maybe I edit
> > a figure caption (knitr option fig.cap=<R character object>), equations,
> > or text. When I am ready to see the formatted doc, I export via ravel,
> > knit, and view. The cached objects get rebuilt as needed.
> Ah. I think I follow this. If you knit the exported .org -> Rmd file
> in the same R session that Org is using, if you change the .org and
> re-export to .Rmd, knitr is smart enough not to re-run the code? Is
> that what you mean? 

Almost. ox-ravel does not call knitr. The ravel backends advice 
`org-babel-exp-do-export' when a ravel backend runs so R code src blocks 
are not run, but are turned into chunks (for knitr, Sweave, or ...) and 
exported as such. 

When you want to actually process the resulting document, you have to call 
on knitr or some other R report generator to do the work.

> That also must imply that export to .Rmd doesn't
> execute any of the Org babel code, right (otherwise there would be no
> benefit to your workflow since you'd be waiting for Org anyway)?

Correct for R src blocks. But emacs-lisp and other languages are treated as 
under the parent backends.

> If that's the case, I think I could roll with that -- I'd just have
> :eval yes if exporting to .Rmd -> knitr, and do a replace-string to
> :eval no if I was going to export to Beamer.

In R scr blocks, :eval is ignored by ravel and so need not change when 
ravel is run.


> I'm a bit hung up on including non-code-generated images. I'm working
> through one of my presentations to convert to slidify (and may write
> up a Worg tutorial or just one on my blog to add to collective
> knowledge) but am not sure of the right "universal Org syntax" that
> will work with multiple backends. I'm most used to something like
> this:
> #+begin_center
> #+attr_backend :height {6cm, 400px, etc.}
> [[./path/to/image.png]]
> #+end_center
> That's not seeming to work with ox-ravel thus far. I'd love not to
> have to change the Org image syntax to straight markdown just for my
> occasional use of slidify.

It's not related to ox-ravel, which uses the same transcoders as the parent 
backends for everything except inline src and src blocks.

I'm not sure how to get what you seem to want.

Maybe use a custom link 


or ask about html/md links in a fresh thread?



reply via email to

[Prev in Thread] Current Thread [Next in Thread]