similar to: debug 1.2.2 on CRAN

Dear list Can anyone suggest a simple way to abort execution like stop(...) does, but without issuing an "Error: ..." message? I don't want to set 'options( show.error.messages=TRUE)' because I want normal behaviour to resume after this particular stop. (Please reply personally as well as to the list, as I'm not subscribed to R-help) Thanks Mark -- Mark Bravington

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("[.][.]",

'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(

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

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)

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)

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>>)}

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

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

Dear list, I received the response below from the package author of 'debug'. I post it to the list, with Mark's approval, in case it is useful to others too. Regards, Matthew -----Original Message----- From: Mark.Bravington at csiro.au [mailto:Mark.Bravington at csiro.au] Sent: 22 October 2006 23:53 To: Matthew Dowle Cc: Mark.Bravington at csiro.au Subject: RE: Debug package

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)

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

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

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

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.

Hmmm-- still looks like a bug to me! But as I don't want to hog the airwaves, here's my last summary on this point, with a question: [Bravington] #> Prediction from the original data was just an example, of course; my general #> proposal is that inactive factor levels in the prediction set should be #> dropped. I don't see how this could ever cause inconsistent behaviour

> Kevin Wright <kwright@eskimo.com> writes: > > > R 1.9.1 requires multi-line strings to contain a backslash at the > > end of each line (except the last line). As noted by Mark > > Bravington (http://tolstoy.newcastle.edu.au/R/help/02b/5199.html) > > this requirement appears to be undocumented. > > > > In S-Plus 6.2, multi-line strings do

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

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

The following looks like an 'eapply' bug to me: t/subtest> e <- new.env() t/subtest> e$tempo <- quote( 1+'hi') t/subtest> lapply( ls( e), function( x) length( get( x,e))) [[1]] [1] 3 # seems reasonable-- e$tempo is a 'call' object of length 3 t/subtest> eapply( e, length) Error in 1 + "hi" : non-numeric argument to binary operator