similar to: how to send a bug report within ESS

Displaying 20 results from an estimated 10000 matches similar to: "how to send a bug report within ESS"

2001 Sep 07
2
Why does substr<- truncate and not replace...
... when the replacement string is shorter than the portion of the string to be replaced? The documentation to substr (in R 1.3.1) gives me: If the portion to be replaced is longer than the replacement string, then only the portion the length of the string is replaced. And so I try: R> x <- "abcdef" R> substr(x,2,3) <- "xy" #ok R> x [1]
2001 Sep 07
2
Why does substr<- truncate and not replace...
... when the replacement string is shorter than the portion of the string to be replaced? The documentation to substr (in R 1.3.1) gives me: If the portion to be replaced is longer than the replacement string, then only the portion the length of the string is replaced. And so I try: R> x <- "abcdef" R> substr(x,2,3) <- "xy" #ok R> x [1]
2001 Jan 12
1
Histogram for factors
Hi, I keep running into this: R> hist (f) Error in hist.default(f) : `x' must be numeric To which of course something like (simplified but not beyond repair): R> hist.factor <- function (ff) { jj <- table (ff) jb <- barplot (jj, ylab="Frequency", xlab=deparse(substitute(ff))) axis (1, jb, names (jj)) } R> hist (f) is a possible solution. Why is a
2000 May 08
3
eigen broken on AIX with R-devel? (PR#537)
Hi, I get the wrong eigen values on an AIX machine with R-devel of 5/3/00. Here are the results: R> m <- matrix (c(6.8, 2.4, 2.4, 8.2), nrow=2) R> m [,1] [,2] [1,] 6.8 2.4 [2,] 2.4 8.2 R> eigen(m) $values [1] 19.281403 6.337993 $vectors [,1] [,2] [1,] 0.1918866 0.9967987 [2,] 0.9967987 -0.1918866 And for comparison, here is what I get on a Sun (with
2001 Sep 07
2
adding logical vector to data frame
Hello. I'm afraid that I'm missing something very obvious this afternoon... When I add a column to a data.frame (by assigning to a "new" column name a logical vector), I thought that I had (at least) 3 options to do so: R> j <- data.frame (x=1:2) R> j$y <- c(TRUE,FALSE) #assignment 1 R> str(j) `data.frame': 2 obs. of 2 variables: $ x: int 1 2 $ y: logi
2001 Jan 30
1
Disappearing x axis in plot.factor (PR#830)
Hi. While there is an x-axis set up for: > plot.factor(factor(1:3)) this axis is not present for > plot.factor(factor(1:3), col="red") which actually should just be the same as the first plot and call barplot(table(.)), shouldn't it? Where did the ticks and labels go? Note that > barplot (table(factor(1:3)), col="red") has the x-axis. Something funky is going
2001 Jan 30
1
screen can't go back to log="y" plot (PR#831)
[I have abbreviated the subject as jitterbug has been having probems with long subjects.] The issue here is that one cannot mix log/non-log axes in the calls to screen(), as the appropriate par() parameter is read-only, but the meaning of yaxp depends on it. But beyond that you can't set x/yaxp for log axes. You should be able to do this: you can in the S original. A simpler version: plot
1999 Jun 10
1
running R on AIX (>= 4.2)
(Was: r-help -- dynload for R on AIX) Thanks for all the responses. Let's see: - I found the dynload.c posted by Arne (April 99, I believe). If the difference to the current version of dynload.c is too big, then the current dynload.c is a better starting point. Otherwise #ifdef's won't be feasible. - One problem appears to be the list of exported symbols.
2001 Feb 13
0
devX11.c -- questions about expose events and XBell
Hi, sorry for lumping this together... Both these issues are rather small, and I'm not sure either qualifies as a bug... 1) After a window id created in X11_Open and mapped, you "gobble the expose events". Not true, you gobble any event that comes along! The code below fixes this by using *XCheckTypedEvent*. Hmm, I'm not sure this right already, but better... ***
2000 Mar 18
3
AIX fails on startup with R-1.0.0
Hi, this is not a bug report since this may not be a problem with R per se. The current release of R (1.1.0) will compile cleanly on an AIX box (I have 4.3.2) but it will fail upon startup with an Illegal Instruction. I've located the problem to be in do_strsplit when R calls regcomp. This function is defined in regex.c. However, the text from regex.o doesn't find its way into the
1999 Jun 09
1
R on AIX (>4.2)
Hi, I'm determined to get R compiling & running on a machine running AIX 4.2. I've seen previous emails in the archive about this topic. The main obstacle is getting dynamic loading to work, but it works for Tcl and hence is feasable. Questions: - is anybody _currently_ working with R on AIX? - why have previous fixes to the sources not been introduced into the released
1999 Jun 09
1
R on AIX (>4.2)
Hi, I'm determined to get R compiling & running on a machine running AIX 4.2. I've seen previous emails in the archive about this topic. The main obstacle is getting dynamic loading to work, but it works for Tcl and hence is feasable. Questions: - is anybody _currently_ working with R on AIX? - why have previous fixes to the sources not been introduced into the released
2001 Feb 03
1
tk non-widget commands (esp. update and winfo)
Hi, I've been playing with the tcltk package. It's very nice to have access to buttons, menus etc. now. Thank you! Alas, I also have questions: In Tcl everything is a string [*]. This is not the case in R, of course. So why are return values of tk commands still strings? (Is there any other reason than speed or "package is work in progress"?) Example: > tt <-
2001 Feb 15
3
who frees dd and xd in X11_Open?
Hi, I'm not sure this is a bug in the code, the comment or my thinking. So first try goes to r-devel... I find the following comment in X11_Open () (src/unix/X11/devX11.c): /* if we have to bail out with "error", then must free(dd) and free(xd) */ A couple lines down, there is: if (!strncmp(dsp, "png::", 5)) { FILE *fp; #ifndef HAVE_PNG error("No png support
2001 Jan 30
0
screen can't go back to (split) screen with log="y" plot (PR#831)
Hi. Let's try to explain the subject line with some code: > split.screen (c(2,1)) [1] 1 2 > screen(1) > plot (1:2, 1:2, log="y", main="1") > screen (2) > plot (1:2, 1:2, main="2") > screen (1) Error in par(.split.screens[[n]]) : invalid value specified for graphics parameter "yaxp". > close.screen(all=TRUE) Let's add comments:
2001 Feb 01
0
screen doesn't handle redrawing properly (PR#837)
Hi. As far as I understand it, there is a list of graphic primitives stored for a device. So for example, when I iconify/deiconify an X11 window, the plot will be redrawn. Now screen (split.screen and friends) appear not to handle this list properly, the list is reset or not reset at odd times. The commands below will show clearly what I mean. There are two effects: - After splitting the
2000 Apr 07
1
x11 colortype problems ('gray' is broken?) (PR#512)
Hi, I occasionally run out of color in my X11 terminal. At this point, R will issue this error message: Error: X11 cannot allocate additional graphics colors. Consider using colortype="pseudo.cube" or "gray". An immediate x11(colortype="pseudo.cube") doesn't work as the colortype seems to be shared among the different x11 plotting windows. So I have
1999 Jul 20
2
R 0.65 and AIX: if it quacks like a duck...
Hi, this relates to R-devel of 1999/July/18. I will outline what I had to change to get R to compile with cc then with gcc. Note that R compiled with cc works, R compiled with gcc is broken. --> Compile with cc: 1) Edit src/main/saveload.c: disable the undefine! With the #undef _XOPEN_SOURCE_EXTENDED the compilation dies an untimely death. (And the header files are not as badly broken
2001 Feb 03
1
callback environment for Tk buttons
Hi. I'm running into problems with using R functions as callback commands for buttons in Tk. The following Tcl/Tk script creates three buttons. If you press hello it prints hello world. If you press HALLO it prints HALLO WORLD. Not exciting, but I need an example... set tt [toplevel .tt] foreach i {"hello" "HALLO"} { pack [button $tt.b$i -text $i
2001 Aug 23
0
(PR#1065) X11 protocol errors after all x11 devices are
I've fixed the original report and Tom's first. Someone had incorrrectly arranged for most of the initialization to be done only once per session. I did ask before 1.3.0 what the intention was .... For pseudocolor devices at least this was biting since the palette was not re-initialized. I don't see point two on my system, and Martin's point about interruption was first shown