Hi, Uwe et al.:
The sos vignette sos.Rnw now fails on GitHub, complaining of a LaTeX
error in "{\tt pspline_ checker}". I don't find it in the code for
sos.Rnw. It may be triggered by a response to an internet search that's
different from before.
https://github.com/sbgraves237/sos
Florian,
ok, understood. It works for me on both M1 build machines, so can't really
help. I'd simply submit the new version on CRAN. Of course it would help if the
tests were more informative such as actually showing the values involved on
failure so you could at least have an idea from the
On 22/05/2023 3:07 p.m., Ivan Krylov wrote:
I fed your vignette to R CMD Sweave, and here's the relevant fragment
from the resulting *.tex file:
This returned a {\tt "findFn"} object identifying 405 help pages.
When this was run while preparing this manuscript, the sixth row was
{\tt
I fed your vignette to R CMD Sweave, and here's the relevant fragment
from the resulting *.tex file:
> This returned a {\tt "findFn"} object identifying 405 help pages.
> When this was run while preparing this manuscript, the sixth row was
> {\tt pspline_checker} in the \pkg{JOPS} package, which
Hi, Uwe et al.:
Uwe suggests I postprocess output with gsub("_", "_", output).
It's not clear to me where I should apply this. The "WARN" flags the
sos vignette sos.Rnw, but the offending code refers to pspline_checker,
which is not in the version of the vignette available on
A simple fix might be to redefine findFn in the global environment of the
vignette, have it explicitly call sos::findFn, and return a result
sanitized for LaTeX output. According to this:
https://stackoverflow.com/questions/32865384/function-to-sanitize-strings-for-latex-compilation
it looks like
Dear Duncan and Simon,
thank you both very much for you help.
I can make the test more informative and also break it down into substeps. But
I am unsure whether CRAN policies allow to use their system for such testing
steps. I rather think not. Though I must say that I still do not know how to
