similar to: (PR#3658)

Displaying 20 results from an estimated 2000 matches similar to: "(PR#3658)"

2004 Dec 06
0
a better "source(echo=TRUE)" {was "....how to pause...."}
You might want to have a look at 'source.mvb' & friends in the 'mvbutils' package. It's designed to allow control of nested sourcing, and to allow interspersed data and commands in a single self-contained file. Unlike 'source', 'source.mvb' reads each statement and immediately executes it, before proceeding to the next; hence it has do the parsing to figure
2005 Feb 11
3
getAnywhere and functions starting with "." (PR#7684)
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)
2003 Mar 26
0
termplot (PR#2687)
# r-bugs@r-project.org `termplot' bombs if the original dataset contains NAs in the predictors, even if these were ignored during fitting: test> bug.data_ data.frame( x=c(1:3, NA), y=runif( 4)) test> lm.tpbug_ lm( y~x, data=bug.data) test> termplot( lm.tpbug) Error in xy.coords(x, y, xlabel, ylabel, log) : subscript out of bounds A simple fix seems to be add the
2002 Dec 27
0
parse and pushBack (PR#2396)
Is this the last bug of the year? Well, it's the last one from me, anyway... The "parse" function seems to give erratic behaviour when used in conjunction with "pushBack" on an open connection (R1.6.1, Windows 2000). Try this: > { cat( c( '1', 'a+b', '2'), file='r123.r', sep='\n'); tcon_ file( 'r123.r'); open( tcon);
2003 Oct 28
0
data.frame replacement (PR#4820)
When replacing all elements of a column in a data.frame, a corrupt data.frame will be generated if the replacer is "short": test> bbb <- data.frame( x=1:2) test> bbb[,'x'] <- 3 # should fill the column test> bbb x 1 3 2 <NA> Warning message: corrupt data frame: columns will be truncated or padded with NAs in: format.data.frame(x, digits = digits)
2003 Sep 25
1
tkinsert (PR#4289)
In R-1.7.1, I used to be able to append a character vector to a 'tklistbox' with e.g. listio <- tklistbox( tktoplevel(), font='Courier', height=20, width=20, setgrid=TRUE) tkinsert( listio, 'end', letters[1:3]) tkpack( listio,side='left', expand=TRUE, fill='both') and three items would be added to 'listio'. This doesn't work in R-devel-- it
2003 Sep 24
1
getAnywhere (PR#4275)
'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(
2009 Oct 16
0
post-installation startup problem with 2.10.0
I've just installed R2.10.0 v50082, and found the problem described below the first few times I launched it. Did not occur with v49613 (the previous most recent version I have). The problem has now gone away, and is therefore non-reproducible, but there seems to be something up with parameter processing or environment variable checking or loading of .RData files immediately after installation.
2009 Oct 19
0
weird warning in [.data.frame with 2.10
I'm getting the following warnings under 2.10 v50082 but not v49613 >> In addition: Warning messages: 1: In `[.data.frame`(df, -(1:nrow(df)), , drop = FALSE) : named arguments other than 'drop' are discouraged 5: In `[.data.frame`(object, !omit, , drop = FALSE) : >> named arguments other than 'drop' are discouraged In neither case are there any named arguments,
2003 Mar 26
5
predict (PR#2686)
# 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),
2003 Mar 26
2
predict (PR#2685)
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(
2002 Sep 19
3
savehistory directories and quitting R (PR#2038)
# # 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
2004 Mar 09
3
update forgets about offset() (PR#6656)
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,
2016 Dec 12
0
[RE: why does parent.frame() cycle when called from inside capture.output()?]
Thanks, Mark - I'm taking up your invitation to forward your message to the list just because it gives us some valuable data on (1) how long the behavior has been around, and (2) how many other people (don't) understand the behavior, and (3) how we might fix or work around it. I notice some other people also seem to be diffident about posting on R-devel; perhaps I should conclude that
2004 Jan 22
0
FW: Réf. : Packages debug and mvbutils
Please use the CRAN versions, not the ftp versions which are now out-of-date. Both packages are on base CRAN now, but may not have propagated to all mirrors yet. (But thanks to Gerald for responding-- I had de-subscribed from R-help.) For anyone using the HANDY package (a Windows-specific package which includes a non-C DLL, so I can't CRAN it): I'll post an updated version on the ftp site
2004 Sep 21
0
checking for _non-existing_ -> documentation and sources at one place.
Wolski wrote: #>>>Has anyone a tool which is able to generate from #>>>#appropriately commented R-code files (e.g. <<example>>= #>>>#-example section) Rd files: Mark Bravington mentioned something similar in the 'mvbutils' package: Wolski wrote: # # #Hi! # #Is it working with S4? Mark's reply: Don't know whether it works with S4
2010 Apr 14
0
mvbutils 2.5.1 on CRAN
Version 2.5.1 of 'mvbutils' is now on CRAN. This version offers improved support for easy package preparation and maintenance, plus minor changes required by the new version of the 'debug' package (see separate announcement). Package 'mvbutils' offers the following main features, as well as a number of miscellaneous goodies: - Hierarchical organization of projects (tasks)
2010 Apr 14
0
mvbutils 2.5.1 on CRAN
Version 2.5.1 of 'mvbutils' is now on CRAN. This version offers improved support for easy package preparation and maintenance, plus minor changes required by the new version of the 'debug' package (see separate announcement). Package 'mvbutils' offers the following main features, as well as a number of miscellaneous goodies: - Hierarchical organization of projects (tasks)
2009 Nov 16
0
mvbutils and debug: new versions
New versions of the 'mvbutils' and 'debug' packages are now available on CRAN. These should work with R 2.10 as well as R 2.9. 'mvbutils' offers tools for organization of workspaces, function/documentation editing with backups, package construction and updating, seamless per-object lazy-loading, and various miscellaneous goodies. New in this version: nearly-automated
2009 Nov 16
0
mvbutils and debug: new versions
New versions of the 'mvbutils' and 'debug' packages are now available on CRAN. These should work with R 2.10 as well as R 2.9. 'mvbutils' offers tools for organization of workspaces, function/documentation editing with backups, package construction and updating, seamless per-object lazy-loading, and various miscellaneous goodies. New in this version: nearly-automated