Hello,
On my package's check results (
https://cran.r-project.org/web/checks/check_results_summarytools.html), I
see a bunch of warnings with "No protocol specified" messages. This happens
only with OS X, and I can't reproduce them when actually building on a Mac,
nor with rhub::check_on_macos().
On Mon, 17 Feb 2020 14:56:31 -0500
Duncan Murdoch wrote:
> So how do I capture stderr (or, off topic here, how do I get libGL to
> be quiet)?
libGL seems to only offer bad news in this regard: it writes directly
to stderr [1] and does not seem to offer a way to silence the
_LOADER_FATAL messages
On 17/02/2020 2:56 p.m., Duncan Murdoch wrote:
I'm working on the initialization code for rgl, especially for the case
when it is running remotely and the user is connecting using X11.
On some machines, this fails: I now understand that's because the local
machine needs to enable "indirect GLX"
I'm working on the initialization code for rgl, especially for the case
when it is running remotely and the user is connecting using X11.
On some machines, this fails: I now understand that's because the local
machine needs to enable "indirect GLX" (IGLX) for it to succeed, and by
default mos
latex() probably stopped midway through the compilation because you are
using intermediate routines other than the default.
For pdflatex, for example, you need to run
options(latexcmd='pdflatex', dviExtension='pdf', xdvicmd='open')
before using the latex() function. See the Details section of
I don't think it is possible to avoid exporting S3 methods from a package and
still have the class behave as intended. Use a regular function if name
encapsulation is important to you.
On February 17, 2020 8:33:30 AM PST, b...@denney.ws wrote:
>Thanks for the pointer! Adding
>"S3method(knit_pri
Thanks for the pointer! Adding "S3method(knit_print_helper_formula,name)" to
the NAMESPACE seems to have fixed it.
For others who come across this, in roxygen2 parlance, that means using:
#' @method knit_print_helper_formula name
#' @export
Even though the actual export is not desired.
Thanks
Hi Rich,
I’m not doing the same thing as Hmisc::latex(). That generates a .tex file and
compiles it (or at least it appears to try to do that on my system, but it
stopped partway through for me).
When I ran
Hmisc::latex(a~b)
It generated a .tex file for a table:
\begin{table}
Please be consistent with the latex() function in the Hmisc package. For
example, for an array x, latex (x) produces a complete latex table
environment. See the ?latex helpfile for details.
Rich
On Mon, Feb 17, 2020 at 10:07 wrote:
> Hello,
>
>
>
> I'm working on a function in a package that
On 17/02/2020 10:05 a.m., b...@denney.ws wrote:
Hello,
I'm working on a function in a package that will provide an exported
function that will convert formula to LaTeX equations. For that, it
recursively goes through the formula converting objects of class "formula",
"call", "name", and "(
Hello,
I'm working on a function in a package that will provide an exported
function that will convert formula to LaTeX equations. For that, it
recursively goes through the formula converting objects of class "formula",
"call", "name", and "(" to LaTeX.
I have a private S3 generic function
11 matches
Mail list logo
