similar to: Feature request: display file name in R CMD check warning

On Thu, Jul 12, 2018 at 2:21 PM Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > I think I found the bug. The tools::checkRd function only processes > \Sexpr's with "stage=render". I think the author (who might have been > me, I forget) assumed that would imply all the earlier stages as well, > but apparently it doesn't. > > So you could use that as

On 12/07/2018 9:46 AM, G?bor Cs?rdi wrote: > On Thu, Jul 12, 2018 at 2:30 PM G?bor Cs?rdi <csardi.gabor at gmail.com> wrote: >> >> On Thu, Jul 12, 2018 at 2:21 PM Duncan Murdoch <murdoch.duncan at gmail.com> wrote: >>> I think I found the bug. The tools::checkRd function only processes >>> \Sexpr's with "stage=render". I think the author

On Thu, Jul 12, 2018 at 12:23 PM Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > > On 12/07/2018 6:33 AM, G?bor Cs?rdi wrote: > > I would like to create \examples{} in the manual dynamically, and > > while it is possible to do this with a \Sexpr at the top level, R CMD > > check issues a warning for it. (See below.) > > > > Is it intentional that

----- Original Message ----- > From: "Simon Urbanek" <simon.urbanek at r-project.org> > To: "Dan Tenenbaum" <dtenenba at fredhutch.org> > Cc: "R-devel" <r-devel at r-project.org> > Sent: Monday, January 12, 2015 5:50:35 PM > Subject: Re: [Rd] R CMD build looking for texi2dvi in the wrong place (R-devel) > > Dan, > > On

Thank you Dan but it isn't my tests that are failing (all of them pass without problem) but one of the examples from the inst/examples directory. I did try, however, to start R with the environmental variables as you suggest but it had no effect on my tests. Charles On Wed, May 13, 2015 at 1:51 PM, Dan Tenenbaum <dtenenba at fredhutch.org> wrote: > > > ----- Original Message

Well, I'm getting a warning (not an error) when the package doesn't exist. I interpreted "most often" to mean that suppressing warnings/errors is why you'd most often use this argument, as most packages don't emit startup messages. And technically there isn't a problem with attaching the package, since we don't even try to attach packages that don't exist.

R CMD build fails with recent R-devel because it is looking for texi2dvi in /usr/local/bin, but on this system, MacTex has installed it in /usr/bin. $ R CMD build IRanges * checking for file 'IRanges/DESCRIPTION' ... OK * preparing 'IRanges': * checking DESCRIPTION meta-information ... OK * cleaning src * installing the package to build vignettes * creating vignettes ... ERROR

Hello, When running tools::checkRd() on a single .Rd file, should I expect the output to be the same as that generated by R CMD check when it checks .Rd files? R CMD check finds the following warning: * checking Rd \usage sections ... WARNING > Assignments in \usage in documentation object 'ilm': > result <- ilm(celfiles, threshold = 350, satLim = 10000) > Functions with

Dear developers, I came across with a bug while parsing Rd files. Given is the following minimal Rd file: ---- \name{foo} \title{foo} \description{ #ifdef windows win #endifd #ifdef unix unix #endif } ---- By accident I have a typo at line 6, instead of having #endif I typed #endifd. If I run checkRd(), parse_Rd(), Rd2HTML(), or others including the command line "R CMD Rconv" R

Hi-- I googled the above error and found previous postings about this error on the list. I was having a little difficulty implementing the advice though. The suggestions were to use: traceback() and checkRd(). I'm using R in the directory in which the .Rd file with the problem is located, but I'm having difficulty figuring out how to proceed. I've looked through the help pages for

On Thu, Jul 12, 2018 at 2:30 PM G?bor Cs?rdi <csardi.gabor at gmail.com> wrote: > > On Thu, Jul 12, 2018 at 2:21 PM Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > > I think I found the bug. The tools::checkRd function only processes > > \Sexpr's with "stage=render". I think the author (who might have been > > me, I forget) assumed that

I'm trying to R CMD check a package, and I'm getting the 'checking S3 generic/method consistency' warning. I have written a function 'gamma.dist' which is _not_ an S3 method, but happens to collide with the 'gamma' function from the R::base namespace. Is there a way of telling CMD check that the name is intentional and is not meant to be an S3 method? My function

On 12/07/2018 7:30 AM, G?bor Cs?rdi wrote: > On Thu, Jul 12, 2018 at 12:23 PM Duncan Murdoch > <murdoch.duncan at gmail.com> wrote: >> >> On 12/07/2018 6:33 AM, G?bor Cs?rdi wrote: >>> I would like to create \examples{} in the manual dynamically, and >>> while it is possible to do this with a \Sexpr at the top level, R CMD >>> check issues a

Hi, The `quietly` argument of `require` is documented as follows: quietly: a logical. If ?TRUE?, no message confirming package attaching is printed, and most often, no errors/warnings are printed if package attaching fails. However: > require(foo, quietly=TRUE) Warning message: In library(package, lib.loc = lib.loc, character.only = TRUE, logical.return = TRUE, :

On 10/03/2015 3:17 PM, Duncan Murdoch wrote: > On 10/03/2015 2:56 PM, Dan Tenenbaum wrote: > > > > > > ----- Original Message ----- > >> From: "Duncan Murdoch" <murdoch.duncan at gmail.com> > >> To: "Dan Tenenbaum" <dtenenba at fredhutch.org> > >> Cc: "Hsiu-Khuern Tang" <tangoh at gmail.com>, r-devel at

We were also able to reproduce the issue on Windows Server 2012. If there's anything we can do to help please let me know; Elliot Waingold (CC'd here) can provide access to the VM we used for testing if that's of any help. # David Smith -- David M Smith <davidsmi at microsoft.com> R Community Lead, Revolution Analytics (a Microsoft company)? Tel: +1 (312) 9205766 (Chicago IL,

----- Original Message ----- > From: "Uwe Ligges" <ligges at statistik.tu-dortmund.de> > To: "Dan Tenenbaum" <dtenenba at fredhutch.org>, "R-devel at r-project.org" <r-devel at r-project.org> > Sent: Saturday, August 8, 2015 3:57:34 PM > Subject: Re: [Rd] download.file() on ftp URL fails in windows with default download method > >

----- Original Message ----- > From: "G?bor Cs?rdi" <csardi.gabor at gmail.com> > To: "Dan Tenenbaum" <dtenenba at fredhutch.org> > Cc: r-devel at r-project.org, "John McKown" <john.archie.mckown at gmail.com> > Sent: Thursday, March 19, 2015 11:15:47 AM > Subject: Re: [Rd] CRAN binary, but no source > > > > > On

----- Original Message ----- > From: "G?bor Cs?rdi" <csardi.gabor at gmail.com> > To: "John McKown" <john.archie.mckown at gmail.com> > Cc: r-devel at r-project.org > Sent: Thursday, March 19, 2015 9:03:37 AM > Subject: Re: [Rd] CRAN binary, but no source > > On Thu, Mar 19, 2015 at 11:59 AM, John McKown > <john.archie.mckown at

When creating a package, I would like a way to tell R that a function with a period in its name is not a method. I'm writing a package now with a modified version of qr.R. R CMD check gives warnings: * checking S3 generic/method consistency ... WARNING qr: function(x, ...) qr.R: function(qr, complete, pivot) See section ‘Generic functions and methods’ of the ‘Writing R Extensions’