similar to: Bug report (PR#7341)

Full_Name: Dan B Version: R 2.0.0 (2004-10-04). OS: Fedora 2 Submission from: (NULL) (80.6.127.185) The man page for barplot (?barplot) is confusing... <quote> cex.axis: expansion factor for numeric axis labels. cex.names: expansion factor for axis names (bar labels). </quote> What is an 'expansion factor', and what does it do in this context? <quote> axis.lty: the

Full_Name: Dan B Version: 2 OS: Fedora 2 Submission from: (NULL) (80.6.127.185) It would be great if something like currentPlot <- edit(par) allowed dynamic changes to the 'currentPlot', which I am using as some kind of 'magic' keyword in the above context. i.e. the value of 'currentPlot' is actually an alias for whatever the current graphical object is. calling

It is the old story of defined behaviour and expected outcomes. Hard to change now. So I would suggest you do something like this in your ~/.Rprofile: R> smry <- function(...) summary(..., digits=6) R> smry(155555L) Min. 1st Qu. Median Mean 3rd Qu. Max. 155555 155555 155555 155555 155555 155555 R> Maybe call it Summary() instead. Dirk --

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

Signif. codes: 0 *** 0.001 ** 0.01 * 0.05 . 0.1 1 Signif. codes: 0 <80><98>***<80><99> 0.001 <80><98>**<80><99> 0.01 <80><98>*<80> <99> 0.05 <80><98>.<80><99> 0.1 <80><98> <80><99> 1 Signif. codes: 0 *** 0.001 ** 0.01 * 0.05 . 0.1 1 hmm... they go away when I

This has been asked before, but all the answers are hidiously complex. The legend.text=TRUE option of barplot is almost exactly what I need, except I need a legend.placement='tl' (top left) option. This option would be in contrast to the default placement which we could call 'tr' (top right). Anyone know how to edit the barplot code to make this change? Could someone like me

Hello all, It seems that the next improvement to the R Graph Gallery is categorization of the graphics, that way each graph will be easier to find. That step should be done *carefully* if we want to avoid the opposite side-effect : graph not reachable through the categories. That's why the wisdom of the R community is required. Graphics will be classified in : - categories -

Hello, supposing that I have two or three clear categories for my data, lets say pet preferece across fish, cat, dog. Lets say most people rate their preference as being mostly one of the categories. I want to do pca on the data to see three 'groups' of people, one group for fish, one for cat and one for dog. I would like to see the odd person who likes both or all three in the

Hi, I want to use hist with non-equi-spaced breaks, picked such that the fraction of the data points falling in the cells (defined by 'breaks') is roughly equal accross all cells. Is there such a function that will automatically try to determine the breaks to fullfill this requirement? Something like.. hist( x, br = magic_function_to_pick_breaks()) For example, if x looked like

I want to add values onto the end of a vector, for example... x <- vector for (i in 1:5){ add_to_end_of_vector(i,x) } I just cant find the answer to this question! Sorry for such a basic question, I tried... x <- c() for (i in 1:5) x[length(x)] <- i but it didn't work.

At 10 Sep 1999 06:53:01 -0000, Mitsuru Oka <oka@debian.or.jp> wrote: > > > I found problem in R-0.65.0/src/scripts/R.sh.in script. > When I run R program with `R -d gdb', R script say, > > /usr/local/bin/R[104]: shift: bad number > > I fixed this problem by applying following patch to the script: ... > > Version: > platform = i586-unknown-linux

> # creating a file > cat("sddfasdf", file="tempfile") > showConnections() class description mode text isopen can read can write > con <- file("tempfile", "r") > readLines(con) [1] "sddfasdf" Warning message: incomplete final line in: readLines(con, n, ok) > showConnections() class description mode text isopen