Re: [R] [RE: [Rd] why does parent.frame() cycle when called from inside capture.output()?]

Hi Frederik Goodo, glad you found mvbutils::mvb.parent.frame useful. I had forgotten that it's in mvbutils rather than debug package. This all dates back about 15 years... To be fair, I don't think R's behaviour with duplicated-but-aliased frames in the call stack is a "bug"--- everything norm

Re: [R] graphic problem: transparent window when starting mtrace() from package debug

Hi Jannis [I'm the author of package debug... I know this is 6 months after your query, sorry-- but I don't subscribe to R-help, and you didn't post to the maintainer! I'm primarily sending this to close off the thread.] > when I use the package debug, mark a function with mtrace() and enter >

Re: [R] mtrace function

Thanks for passing that on, Uwe. There are two separate things here: - Uwe's problem is a bug: there is an experimental source-code-debugging feature in 'debug' that doesn't work properly yet (pending a change in the 'parser' package) and for some stupid reason I'd set the default to "use exp

[R] [R-pkgs] debug 1.2.2 on CRAN

Version 1.2.2 of 'debug' is now on CRAN. The debugging facilities offered include code display, graceful error recovery, line-numbered conditional breakpoints, access to exit code, flow control, and full keyboard input. The new version supports debugging of code inside 'try', 'eval', 'evalq', an

[R] [R-pkgs] 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 nu

[R] [R-pkgs] 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

Re: [R] how to stop without error message?

> > 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. > > What's wron

Re: [R] how to stop without error message?

Hi John Using 'on.exit' to reset the "show.error.messages" option should work, but it doesn't quite... and I'm not sure why. It breaks down with, for want of a better phrase, "nested" calls to stop, inside 'try' statements. For some reason, the inner 'stop' calls *do* lead to messages, althoug

Re: [R] how to stop without error message?

Thank you Hadley & John Hadley's approach below is the kind of thing I was expecting-- I'd just never managed to figure out how to use tryCatch. John has also made me think that I could probably patch things up by modifying my calls to 'try'-- because sometimes I do want to print the error mess

[R] how to stop without error message?

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 t

[R] model.matrix consistency across repeated calls

I am using R to construct model matrices that I then pass into C for subsequent fitting. Suppose I have a data.frame so big that, if I called 'model.matrix' directly on the whole thing, the results would be too big to handle (because factors expand to multiple columns, etc.). Instead, I really wan