similar to: Bug list summary (automatic post)

================================================= 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

Rashid Nassar <rnassar@acpub.duke.edu> writes: > I have one more nitpick, if I may: > > summary(aov.obj) prints significance *'s but doesn't print the legend > at the bottom explaining their meaning (it is not parallel with > summary(lm.obj) > > > Question: Is this kind of nitpicking feedback useful (if so I'd be > glad to continue to keep notes and

================================================= 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

On Mon, 28 Aug 2000, Rashid Nassar wrote: > Dear Professor Ripley, > > Thank you very much for your kind explanation. If I may lamely say > something in my defence, even as I apologize for my error: I mistook the > sentence "the (quoted) name of a function" to mean "optionally quoted" > because of the parentheses surrounding "quoted", and was

Thanks for your reply Nassar. What I really want is to overlay (like add=TRUE) the plots 1 and 2. With plots "at the same screen" I meant overlaid and not one beside the other, i.e., only one plot with all the points (1 to 10) in blue (or any other color), the points 5 to 9 in red and a regression line from points 5 to 9. Best regards, Antonio Olinto ----- Original Message -----

R-devel Digest Monday, September 24 2001 Volume 01 : Number 314 In this issue: [Rd] R 1.3.1 fails 'make check' on arm in the Bessel example (PR#1097) [Rd] Bug list summary (automatic post) [Rd] (PR#1089) Can be closed See the end of the digest for information about r-devel-digest ---------------------------------------------------------------------- Date: Fri, 21

1. THANK YOU! to all who make R possible. It is a real joy to use. 2. The following may or may not be (minor) bugs, but I thought I'd mention them anyway: (a) model.matrix() seems unduly finicky: it seems to accept only "simple" variable names (x1, but not, say, dframe$x1 or I(x1^2), for example) in its argument. model.frame(), however, has no problem with these. (b) If A is a

On Fri, 14 Nov 1997, Jim Lindsey <jlindsey at luc.ac.be> sent an email to r-devel describing his first shot at porting Design and Hmisc to R. A few days later, his port snapshot of Design was uploaded to CRAN's src/contrib/devel area, and has since been available from there. A few weeks ago, Andreas Weingessel <A.Weingessel at ci.tuwien.ac.at> had a look into porting Hmisc to R

yes I have tries, and nothing. It just shows the strings with the slashn, just like i typed it. -----Original Message----- From: Rashid Nassar [mailto:rnassar at duke.edu] Sent: ÐÝì?ôç, 16 Óå?ôåìâñßïõ 2004 15:44 To: Christos Rodopoulos Subject: Re: [R] How do I insert a newline in my title in a plot? Have you not tried what you have already suggested: title("this is a title\nIn 2

platform: Linux Mandrake 10.0 AMD processor, X11 graphics with XFree latest, R version 1.9.1 home-compiled. -----Original Message----- From: Prof Brian Ripley [mailto:ripley at stats.ox.ac.uk] Sent: ??????, 16 ??????????? 2004 16:27 To: Christos Rodopoulos Cc: 'R-help at stat.math.ethz.ch' Subject: Re: FW: [R] How do I insert a newline in my title in a plot? On Thu, 16 Sep 2004,

Some observations as feedback on minor points that I came across while enjoying [R-0.62.2]: 1. par(bty="n"): sometimes (depending on data) points appear to "spill out" of the plot using default xlim and ylim values (are default axes a bit too short?) 2. points(x,y,pch="c") allows points to plot outside existing plot box (an interesting feature, but may be a bug?);