Displaying 5 results from an estimated 5 matches for "run_one_vignett".
Did you mean:
run_one_vignette
2012 Dec 10
1
Generate .Rout.save files for vignettes
...with the target output file."
Yet, there is no pointer on how to get the correct .Rout.save files for
vignettes. (For the files in directory "test" there is a footnote on how
to get the .Rout.save files. [2])
As a temporary solution, we currently use a script that calls
tools:::.run_one_vignette() on each vignette and dumps the output:
echo 'tools:::.run_one_vignette("vignette.Rnw", docDir = ".");' | R
--vanilla > vignette.Rout.save
However, this doesn't result in the same code as produced by R CMD
check. E.g., we get the R startup header and further...
2014 Dec 10
2
UTF8 markdown vignette
...tps://github.com/wch/r-source/blob/e721ef5f4/src/library/tools/R/Vignettes.R#L507
> Apparently only the file and quiet arguments are passed to the
> vignette engine. Did I miss anything?
I think it's actually a little messier than that: sometimes the
encoding is passed (e.g. by tools:::.run_one_vignette, used in R CMD
check), but not always. Here's what I think should happen instead:
When building a vignette in a package, R knows the encoding declared for
the package, so it should assume this as the default for the vignette.
If nothing is declared, it should assume "native.enc", i...
2014 Dec 19
1
UTF8 markdown vignette
...f4/src/library/tools/R/Vignettes.R#L507
>>> Apparently only the file and quiet arguments are passed to the
>>> vignette engine. Did I miss anything?
>>
>> I think it's actually a little messier than that: sometimes the
>> encoding is passed (e.g. by tools:::.run_one_vignette, used in R CMD
>> check), but not always. Here's what I think should happen instead:
>>
>> When building a vignette in a package, R knows the encoding declared for
>> the package, so it should assume this as the default for the vignette.
>> If nothing is declared...
2014 Dec 18
0
UTF8 markdown vignette
...-source/blob/e721ef5f4/src/library/tools/R/Vignettes.R#L507
>> Apparently only the file and quiet arguments are passed to the
>> vignette engine. Did I miss anything?
>
> I think it's actually a little messier than that: sometimes the
> encoding is passed (e.g. by tools:::.run_one_vignette, used in R CMD
> check), but not always. Here's what I think should happen instead:
>
> When building a vignette in a package, R knows the encoding declared for
> the package, so it should assume this as the default for the vignette.
> If nothing is declared, it should assume &...
2014 Dec 09
3
UTF8 markdown vignette
On 09/12/2014, 4:38 PM, ONKELINX, Thierry wrote:
> Dear Yihui,
>
> I have created a reproducible example at https://github.com/ThierryO/utf8vignette
>
> The \usepackage{} line is needed, otherwise R CMD check --as-cran will give a warning.
> %\VignetteEncoding{UTF-8} did not solve the problem.
I've just taken a look at the sources, and that's only in R-devel, it
never