similar to: enhancement request for browser (PR#8706)

Displaying 20 results from an estimated 10000 matches similar to: "enhancement request for browser (PR#8706)"

2006 Mar 17
3
Open .ssc .S ... files in R (PR#8690)
----- Quick summary: In the File:Open dialog, please change "S files (*.q)" to "S files (*.q, *.ssc, *.S)" and show the corresponding files (including .SSC and .s files). ----- Background This is motivated by the following query to R-help: >Date: Thu, 16 Mar 2006 22:44:11 -0600 >From: "xpRt.wannabe" <xprt.wannabe at gmail.com> >Subject: [R] Is
2005 Nov 09
0
R CMD Rdconv file.Rd --type=Ssgm \code{x} should use <code> (PR#8290)
I'm trying: R CMD Rdconv file.Rd --type=Ssgm If file.Rd contains \code{x} then this is currently translated as <s-expression>x</s-expression> I suggest instead translating to <code>x</code> (provided that R CMD Sd2Rd is changed to support the <code> tag; I just submitted that bug separately). Note that this is an enhancement, not a bug. This change would
2008 Feb 22
0
R CMD check for glmpath on Windows (PR#10823)
The problem first appeared in R 2.6.1 and is still there in R 2.6.2 On Windows running R CMD check command for glmpath package fails. The reason seems to be that when R is running the examples file (glmpath-Ex.R), it skips about 50 lines and as a result gives a syntax error. I'm working with a modified version of the CRAN glmpath 0.94. My version happens to give a more clear example of a
2008 Jun 11
0
[ESS] browser() exits when not desired, in three different scenarios (PR#11634)
Tim, I have reported some similar issues a while back and there was some discussion on this topic: http://tolstoy.newcastle.edu.au/R/devel/06/03/4609.html Good luck, Kevin On Tue, Jun 10, 2008 at 6:47 PM, Tim Hesterberg <timhesterberg at gmail.com> wrote: > Here are three different scenarios in which the browser() exits > when I don't want it to. These are all related to the
2008 Feb 09
1
bad variable names when printing a data frame containing a matrix (PR#10730)
library(glmpath) data(heart.data) # heart.data is a list, $y a vector, $x a matrix data <- data.frame(x=I(heart.data$x), y = heart.data$y) > data[1:2,] x.1 x.2 x.3 x.4 x.5 x.6 x.7 x.8 x.9 y 1 160 12 5.73 23.11 1 49 25.3 97.2 52 1 2 144 0.01 4.41 28.61 0 55 28.87 2.06 63 1 > dimnames(heart.data$x)[[2]] [1] "sbp"
2008 Feb 06
0
Suggestions for R-intro manual (PR#10701)
Some suggestions for R-intro: -------------------------------------------------- Section 9.2.2, change: (Note the function split() which produces a list of vectors obtained by splitting a larger vector according to the classes specified by a factor. This is a useful function, mostly used in connection with boxplots. See the help facility for further details.) Warning: for() loops are used in
2006 Jul 06
1
comment causes browser() to exit (PR#9063)
I'm trying to step through some code using browser(), executing one line at a time. Unfortunately, whenever I execute a comment line, the browser exits. I previously reported a similar problem with blank lines. These problems are a strong incentive to write poor code -- uncommented code with no blank lines to improve readability -- so that I can use browser() without it exiting at
2008 Jun 10
0
browser() exits when not desired, in three different scenarios (PR#11623)
Here are three different scenarios in which the browser() exits when I don't want it to. These are all related to the browser accepting either c or (return) to exit. I would like an option to turn off the (return) behavior in order to avoid these problems. # Case 1 - when calling help # Note, I am using ESS in emacs; this is probably an interaction # with ESS handling of ? help. > f
2009 Sep 23
0
warnings handled oddly in functions with browser calls (PR#13967)
Full_Name: Rich Calaway Version: 2.9.2 OS: Windows Vista Submission from: (NULL) (65.47.30.18) Consider the following function: myfun <- function(){ print(log(-1)) browser() print("Good-bye!") } In the default case, with options(warn=0), if I call this function and type nothing but standard browser commands (c, n, where, Q) at the browser prompt, the warning produced by log(-1)
2008 Jan 24
0
deprecate "freq" argument to hist
I request that the "freq" argument to hist be deprecated. Reason: One nice thing about SAS is is the consistency of certain inputs across many PROCs. In particular, they have "weight" and "freq" statements. We have added "weights" and "freq" to a number of functions in S-PLUS, listed below. I would like to see the same in R. In porting the
2006 Feb 04
1
Using the lazy data mechanism
Dear list members, I'm trying to use the lazy data mechanism with the car package, so far without success. The data sets are in the source package's data subdirectory in the form of compressed .rda files, and I added the directive LazyData: yes to the package's DESCRIPTION file. I suspect that the problem is that the package has no namespace, but I've been unable to find a
2010 Jul 11
2
Interrupt R?
How can one interrupt the following gracefully: while(TRUE){ Sys.sleep(1) } In R2.11.1 under Emacs+ESS, some sequence of ctrl-g, ctrl-c eventually worked for me. Under Rgui 2.11.1, the only way I've found was to kill R. Suggestions on something more graceful? Beyond this, what would you suggest to update a real-time report when new data arrives in a certain
2016 Dec 07
0
Strange behavior when using progress bar (Fwd: Re: [R] The code itself disappears after starting to execute the for loop)
Dear Martin and Jon, I can reproduce this problem in the Windows GUI, where I observed it using Jon's program after 75 iterations. I didn't observe the problem in a Windows terminal or under RStudio, letting the program run for more than 200 iterations in each case. My system and session info: ------------- snip --------- > Sys.info() sysname release
2011 Jul 23
0
graphic problem: transparent window when starting mtrace() from package debug
Deal R , when I use the package debug, mark a function with mtrace() and enter into the browser like mechanism of debug a window displaying the code of the marked function with the current line highlighted usually appears. When I use GUIs other than ess or the standard R console sometimes this window is totally transparent so it is not possible to see any code in it. After closing/resizing
2012 May 22
0
dataframe package
A new 'dataframe' package is on CRAN. This is a modified version of the data frame code in R, modified to make fewer copies of the inputs and run faster, e.g. as.data.frame(a vector) makes 1 copy of the vector rather than 3, data.frame(a vector) makes 3 copies rather than 6, and x[, "a"] <- newValue makes (2,2,1) copies of (old data frame, new column, integer vector of
2013 Mar 20
0
Character Encoding: Why are valid Windows-1252 characters encoded as invalid ISO-8859-1 characters?
Something that looks like a bug to me - but as there may be a documented reason I have missed, I wanted to ask about it here first. Please let me know if this looks like something I should submit as a bug, if not, why this behavior is intended. Using RGui v2.15.3, 64bit, on a Windows 7 machine with US English locale You can see the behavior I describe in the following -------------------- >
2010 Oct 25
1
Sweave and absolute escaped backslashed Windows paths in R 2.12.0
I've noticed a change in behavior in R 2.12.0 from 2.11.1 regarding the treatment of absolute paths in the file argument of Sweave in a Windows environment. Consider the minimal Rnw file, attached and reproduced below my signature in case .Rnw files get stripped. This file is stored on my (Windows) computer in H:/My Documents. Using an absolute path with the standard window's
2016 Dec 07
3
Strange behavior when using progress bar (Fwd: Re: [R] The code itself disappears after starting to execute the for loop)
>>>>> Jon Skoien <jon.skoien at jrc.ec.europa.eu> >>>>> on Wed, 7 Dec 2016 11:04:04 +0100 writes: > I would like to ask once more if this is reproducible also for others? > If yes, should I submit it as a bug-report? > Best, > Jon Please Windows users .. this is possibly only for you! Note that I do *not* see problems on
2009 Oct 02
1
suggest enhancement to segments and arrows to facilitate horizontal and vertical segments
I suggest a simple enhancement to segments() and arrows() to facilitate drawing horizontal and vertical segments -- set default values for the second x and y arguments equal to the first set. This is handy, especially when the expressions for coordinates are long. Compare: Segments: < function (x0, y0, x1 = x0, y1 = y0, col = par("fg"), lty = par("lty"), --- > function
2006 Mar 09
1
bugs in simtest (PR#8670)
# R for Windows will not send your bug report automatically. # Please copy the bug report (after finishing it) to # your favorite email program and send it to # # r-bugs at r-project.org # ###################################################### This report is joint from Richard Heiberger <rmh at temple.edu> and Burt Holland <bholland at temple.edu>. Burt Holland is the coauthor