similar to: how to stop without error message?

There is a bug in `predict' whereby the order of variables sometimes gets re-arranged compared to the original fit, and then disaster results. Specifically, the 'variables' and 'predvars' attributes of a 'terms' object get out of synch. This only happens when the terms in the original formula get re-ordered during fitting: test> scrunge.data_ data.frame(

Dear R-devel On my Windows 2000 machine, I can build R-patched but not R-devel (since at least 1/9/2004). An error message pops up during the execution of some R code during "make", as below. In terms of "make" etc., I am totally clueless (not being a user of either Linux or C) and just mechanically follow the instructions in the R documentation; hence I've got no idea

R can run external code in C, C++, Fortran, Delphi, etc., but the R extensions manual only gives limited documentation for anything but C and C++. It would be useful to have a collection of sample code showing how to dyn.load functions written in other languages, if necessary for a variety of different compilers, in case that makes a difference. Does such a collection already exist? If not,

Several times my packages have fallen foul of the latex check at the uploading-to-CRAN stage, creating extra work for Kurt Hornik. I've never bothered trying to get latex working on my own packages (happy with vanilla help) but am told that "latex is the closest thing to a syntax checker for Rd files" and that I should set it up. Now, there is already a latex on my (Windows XP)

I've just had the error below while trying to install a package from source under R2.2.1 and Windows XP. I recall encountering this sporadically in the past. It is a pretty confusing message and took me quite some time to figure out; I've seen queries about it on the R site search, but couldn't find a reply. There's an attempted diagnosis and suggested cure below.

'getAnywhere' is not reporting methods when there are periods in the class name or the generic name (in R-devel). > getAnywhere( 'predict.loess') A single object matching 'predict.loess' was found It was found in the following places registered S3 method for predict from namespace modreg namespace:modreg with value <<...>> > getAnywhere(

Problem below with PCRE grep in R-devel; works fine in R-patched. (Unless there's been an absolutely massive change in rules for updated PCRE version 8.13; jeez I hope not) > grep( '[.][.]', '', perl=TRUE) Error in grep("[.][.]", "", perl = TRUE) : invalid regular expression '[.][.]' In addition: Warning message: In grep("[.][.]",

A bit late for Santa, but on my wish-list nevertheless: is there any chance that "scan" and "readLines" could be extended to take a parameter "until" or "EOF.marker", which would be a character string that (if encountered while reading) would cause the reading to stop, just as if an end-of-file had been found? [But leaving a connection open, so that

I noticed the following today --- str() seems to remove any extra class information added to an environment. > e <- new.env() > class(e) [1] "environment" > class(e) <- c("foo", class(e)) > class(e) [1] "foo" "environment" > str(e) Classes 'foo', 'environment' length 0 <environment> > class(e) [1]

# r-bugs@r-project.org `predict' complains about new factor levels, even if the "new" levels are merely levels in the original that didn't occur in the original fit and were sensibly dropped, and that don't occur in the prediction data either. (At least if `drop.unused.levels' was set to TRUE, which the default.) test> scrunge.data.2_ data.frame( y=runif( 3),

When something gets printed by the "print.default" function, any extra attributes are printed without regard to their class attribute (if any). For example: > x <- 1:3 > attr( x, 'other') <- factor( c( 'cat', 'dog')) > attr( x, 'other') [1] cat dog Levels: cat dog > x [1] 1 2 3 attr(,"other") [1] 1 2 which is perhaps

First of all, thanks to those who've set up R to work so smoothly with Miktex-- even a total Latex bunny like me got it to work instantly, so that for the first time I'm able to run my Rd files through the Latex side of RCMD CHECK. Now the question/buglet. One of my Rd files contains the following: \code{mlazy( <<objname1>>, <<objname2>>, <<etc>>)}

Thanks-- as Duncan Murdoch also noted, R_HISTFILE can be used to solve my problem, as below. BTW it's not easy to find out about R_HISTFILE in the help system or manuals, though, unless you already know it exists-- it only seems to be described under startup options, not things to do with history. However, Duncan's reply did hint at an inconsistency, in that savehistory() defaults to

Dear group I use "restart" in part of my code, in a way that's not easily changed to "try". As I convert code from R1.5.0 to R1.6.1, I'm getting ugly messages; the help system says to contact r-devel, so here I am. This one's a bit complicated-- sorry! The context is inside a debugger (I have an R and S debugger that offers stand-alone code windows, line numbered

I'm encountering excruciatingly slow load times for character vectors in R 2.6.0-- up to 30sec for a 15K file that contains a no-attributes character vector of length ~1e4 and object size ~0.5MB. In R 2.5.1, repeated loads of the same set of files are near-instantaneous. The problem is proving tricky to reproduce consistently from scratch, so I have attached the 3 files used in the examples

Full_Name: Mark Bravington Version: 2.0.1 OS: Windows XP Submission from: (NULL) (140.79.22.104) 'getAnywhere' crashes when its argument starts with a period: > getAnywhere( '.onLoad') Error in exists(x, envir, mode, inherits) : invalid first argument One fix might be to replace the line if ( !is.null(f <- getS3method(gen, cl, TRUE))) { with if ( nchar( gen)

Hi! I have renamed some functions and deleted others. I have noticed that R CMD check complains only about newly added functions, but documented non-anymore-existing functions seem not to matter. I knew about prompt and promptMethods promptClass. They are extremely useful if you are starting to write a package. But what with existing packages that have to be rewritten? Having code and

In R1.7 and above (including R 1.9 alpha), 'update.formula' forgets to copy any offset(...) term in the original '.' formula: test> df <- data.frame( x=1:4, y=sqrt( 1:4), z=c(2:4,1)) test> fit1 <- glm( y~offset(x)+z, data=df) test> fit1$call glm(formula = y ~ offset(x) + z, data = df) test> fit1u <- update( fit1, ~.) test> fit1u$call glm(formula = y ~ z,

I haven't been able to build yesterday's R-devel (or, as a test, R-devel_2005-03-11) on Windows XP. The error message I'm getting is to do with 'arithmetic.c', as shown below. Current R-patched seems to build fine, and I've built previous R-devels from source fairly often in the past-- though I have no understanding whatsoever of what's going on. FWIW the only changes

# # r-bugs@r-project.org # ###################################################### Because I work in different directories, but always want to save my .Rhistory in the same place, I have changed the system function savehistory to this: function (file = "D:/R50/.Rhistory") invisible(.Internal(savehistory(file))) When I use q() to quit R, and it asks me whether I want to