On Sat, 29 Sep 2018 15:31:38 +0200 meik michalke <meik.micha...@uni-duesseldorf.de> wrote: > Am Samstag, 29. September 2018, 10:50:33 CEST schrieb meik michalke: > > i just tested the new preview for RMarkdown documents -- great! i > > used an existing report i wrote a while ago, and it looked like it > > should. > > hm, i'm unable to render the vignette for koRpus, though: > https://github.com/unDocUMeantIt/koRpus/tree/master/vignettes > it complains there's an error reading a file, but i can't find the > temporary files to see what particular call is failing. could be the > apa.csl, and it doesn't change if i setwd() into the script directory > first.
The temp files will be in a directory /tmp/rkward-XXXXXXX/ on linux. But I'll have to admit I have not even started thinking about references to external files. I simply saved the current file to a temporary directory, in isolation. Not sure about the most elegant way to solve this. I suppose it may mean that the input file should remain in its place (only with some temporary name), and only the output file(s) should be written somewhere else. > the R console preview also throws an error regarding the "abstract: > >" line, which it also complains about when i render the vignette for > >roxyPackage: > https://github.com/unDocUMeantIt/roxyPackage/tree/master/vignettes > however, that one is being previewed just fine. The R console preview? That one is mean for previewing plain .R scripts (again, it does not really work as intended, right, now, but essentially it should give you a preview of "Run all"), it will certainly choke on R markup. Regards Thomas
pgpGCVQn3iYbK.pgp
Description: OpenPGP digital signature
