# [ESS] knitr

Yihui Xie xie at yihui.name
Thu Jun 7 15:32:15 CEST 2012

For this specific task, it is not terribly hard to do with knitr, and
it happens that someone asked a similar question a few days ago. Here
is my example: https://gist.github.com/2629886#file_knitr_checkpoint.rnw

Basically you specify a chunk name, and knitr will evaluate all chunks
up to that chunk.

Regards,
Yihui
--
Yihui Xie <xieyihui at gmail.com>
Phone: 515-294-2465 Web: http://yihui.name
Department of Statistics, Iowa State University
2215 Snedecor Hall, Ames, IA

On Thu, Jun 7, 2012 at 9:24 AM, Mathieu Basille
<basille at ase-research.org> wrote:
>
> I also would like very much a partial evaluation. I'm not using knitr yet
> (lack of time, unfortunately), but this should be the same for Sweave if
> it's going to be backend independent. I often find myself willing to Sweave
> (and then compile) the document to a given point (usually when revising a
> Sweave document), and skip the rest of the content of the document (that is,
> at the exception of ending macros such as biblio, some R statements, and
> \end{document}). Ideally, what would be great to me would be a string of
> character to start and stop excluding any content (including LaTeX and R,
> i.e. more general that 'eval=FALSE, echo=FALSE' in every chunk) to
> Sweave/knittr.
>
> Mathieu.