search for: r_keep_pkg_source

...e util gets loaded automatically on startup. After setting keep.source.pkgs to TRUE via options(), detaching util, and reloading it --- still no comments, and attr(vignette,"source") was NULL. The help for options() says that keep.source.pkgs defaults to TRUE if the environment variable R_KEEP_PKG_SOURCE is set to `yes'. So my next experiment was to stop R, set this variable, restart R, and then type ``vignette''. Bingo. Comments appeared, and attr(vignette,"source") was there bigtime. However attr(arima,"source") was still NULL (and of course comments were non-ex...

...20)); #endif SET_TAG(v, install("prompt")); @@ -289,6 +290,10 @@ SETCAR(v, ScalarLogical(0)); /* no checking */ v = CDR(v); + SET_TAG(v, install("check.condition")); + SETCAR(v, ScalarLogical(0)); /* no checking */ + v = CDR(v); + p = getenv("R_KEEP_PKG_SOURCE"); R_KeepSource = (p && (strcmp(p, "yes") == 0)) ? 1 : 0; I'm happy to file this via https://bugs.r-project.org, if preferred. /Henrik -------------- next part -------------- Index: src/library/base/man/options.Rd ==================================================...

Hello, I've tried several times yesterday to build R-devel and I consistently get this error when I "make" : mkdir -p -- ../../../library/base/R make[3]: Leaving directory `/tmp/R-devel/src/library/profile' make[3]: Entering directory `/tmp/R-devel/src/library/base' building package 'base' make[4]: Entering directory `/tmp/R-devel/src/library/base' mkdir -p --

...)); > @@ -289,6 +290,10 @@ > SETCAR(v, ScalarLogical(0)); /* no checking */ > v = CDR(v); > + SET_TAG(v, install("check.condition")); > + SETCAR(v, ScalarLogical(0)); /* no checking */ > + v = CDR(v); > + > p = getenv("R_KEEP_PKG_SOURCE"); > R_KeepSource = (p && (strcmp(p, "yes") == 0)) ? 1 : 0; > I'm happy to file this via https://bugs.r-project.org, if preferred. > /Henrik > ---------------------------------------------------------------------- > Index: src/librar...

Hi all, Does anyone know how to debug S4 methods? In my case I want to find an error in the specc-function of the kernlab-package. As this seems to be a S4-method the normal S3 debugging can't be applied apparently (e.g. debug(s3function.someclass)). So in my case > debug(specc:kernlab) seems only to debug the generic-function: > specc:kernlab function (x, ...)

Hi all, I'm developing an R package and I'd like to load it easly while developing, debugging and testing. I would like to load it without having to install it. Installing it causes me some problems for debugging it, as the code file it is executing it not the one I'm editing. I've seen the function sourceDirectory from R.utils package which works quite fine for me, but would be

Dear R users, i am trying to get the line number of the code where an error is produced. With the options: options(keep.source = TRUE, show.error.locations = TRUE, keep.source.pkgs = TRUE) I have managed to get the error locations to show up when i source the respective files. They do not, however, show up for the same errors when I use installed packages. Do I have to build these packages

...> SETCAR(v, ScalarLogical(0)); /* no checking */ > > v = CDR(v); > > > + SET_TAG(v, install("check.condition")); > > + SETCAR(v, ScalarLogical(0)); /* no checking */ > > + v = CDR(v); > > + > > p = getenv("R_KEEP_PKG_SOURCE"); > > R_KeepSource = (p && (strcmp(p, "yes") == 0)) ? 1 : 0; > > > > I'm happy to file this via https://bugs.r-project.org, if preferred. > > > /Henrik > > > -------------------------------------------------------------...

Can I run R code straight from R src (.R) file instead of .rdb/.rdx? I of course tried simply unzipping tar.gz in the R_LIBS directory but R complains with "not a valid installed package". Real issue: I am very new to R and all, so this could be something basic. I'm trying to use ess-tracebug (Emacs front-end to trace/browser et al). It works great when I trace functions in .R

I have a function in one of my packages that I would like to print using the original source rather than the deparse of the function. The package uses lazy loading and the help page for library (under keep.source) says that keep.source does not apply to packages that use lazy loading and that whether those functions keep the source depends on when they are installed. This package is on R-forge

I think I am whistling in the wind, but is there a modern symbolic debugger for R programmes? I am working through some one else's code, thousands of lines, that has the occasional bug in it, and a lot in my understanding of it. I cannot make setBreakpoint or findLineNum work. I get "No source refs found.". I am starting to loose my mind! A debugger where I could set

There is quite a long piece of code defining a certain function in one of the R packages. I think the code has a bug and I want to get the code into a file so that I can take a proper look, and possibly fix it. how does one do this? (I mean getting the code into a file, not fixing the bug.) I suppose I could copy and paste, but that's a bit error prone for various reasons. I want the same

I read through the "Writing R Extensions" and the "Debugging in R" website (http://www.stats.uwo.ca/faculty/murdoch/software/debuggingR/), looking for some hints about how to solve the issue of debugging problems encountered during the "R CMD check" process, but nothing seems to be mentioned about addressing issues encountered. Specifically, I am working with the R

...nteraction.plot(). o Internal cleanup of lapply()'s C code. o library(), require(), and sys.source() have a new argument ` keep.source = getOption("keep.source.pkgs") '. This defaults to false, but can be set (also for base) to true by setting the environment variable R_KEEP_PKG_SOURCE to "yes" o Par `lty' in lines() now defaults to par("lty") not "solid", for consistency with plot(). o list.files() [aka dir()]: path argument has now default = "." o locator() allows inline graphics parameters (for the plotting it does w...

...nteraction.plot(). o Internal cleanup of lapply()'s C code. o library(), require(), and sys.source() have a new argument ` keep.source = getOption("keep.source.pkgs") '. This defaults to false, but can be set (also for base) to true by setting the environment variable R_KEEP_PKG_SOURCE to "yes" o Par `lty' in lines() now defaults to par("lty") not "solid", for consistency with plot(). o list.files() [aka dir()]: path argument has now default = "." o locator() allows inline graphics parameters (for the plotting it does w...