Manage the knitr preamble definitions correctly.

[finlay]

Knitr output requires a bunch of definitions. These can be included in an included preamble file, or do something cunning in the way we call knit:

 (cd knitr; Rscript -e "library('knitr'); knit('$(<F)')")

[klapaukh]

So I added a knitr.sty file which can be included with \usepackage{knitr}. I don't think I want to make it a standard part of any of the classes as I am not entirely convinced that is totally ok.

[edwardabraham]

Should it be a dragonfly-knitr package?

On 7 May 2014 09:12, Roma Klapaukh [email protected] wrote:

So I added a knitr.sty file which can be included with \usepackage{knitr}.
I don't think I want to make it a standard part of any of the classes as I
am not entirely convinced that is totally ok.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/11#issuecomment-42359484
.

Edward Abraham
www.dragonfly.co.nz
Dragonfly Science, PO Box 27535, Wellington 6141, New Zealand
Level 5, 158 Victoria Street, Te Aro, Wellington
M: +64 21 989 454
T: +64 4 385 9285

[klapaukh]

I shouldn't be dragonfly-knitr because it isn't related to any of the dragonfly stuff. It is just general knitr stuff so that knitr's output works correctly. Normally knitr will insert it itself into your files, but the build process used here often doesn't allow for that.