similar to: subfolders in the R folder

The "good reason" is all the tooling in R doesn't work with subfolders and would have to be rewritten. All the package check and build stuff. And that's assuming you don't want to change the basic flat package structure - for example to allow something like `library(foo)` to attach a package and `library(foo.bar)` to attach some subset of package `foo`. That would require

A quick drive-by-comment: What if 'R CMD build' would have an option to flatten R/ subfolders when building the tarball, e.g. R/unix/a.R R/windows/a.R R/a.R becomes: R/00__unix__a.R R/00__windows__a.R R/a.R ? Maybe that would be sufficient for most use cases. The only thing I can imagine is that source file references (e.g. in check NOTEs) will be toward the latter and not the

Hello: I have a server running CentOS 4.4. I just did a yum update and then rebooted the server. After the reboot, it stops after printing GRUB on the screen. Any ideas what happened? Thanks, Neil -- Neil Aggarwal, (832)245-7314, www.JAMMConsulting.com FREE! Eliminate junk email and reclaim your inbox. Visit http://www.spammilter.com for details.

Hi Hadley, Thanks for the counterpoint. Response below. On Thu, May 16, 2019 at 1:59 PM Hadley Wickham <h.wickham at gmail.com> wrote: > The existing behaviour seems inutitive to me. I would consider these > invariants for n vector x_i's each with size m: > > * nrow(rbind(x_1, x_2, ..., x_n)) equals n > Personally, no I wouldn't. I would consider m==0 a degenerate

Hi, it'd be great if you could update the documentation on the website that some models of the Belkin -UNV series will only work with the megatec(_usb) drivers. I wasted a lot of time on trying to get it to work with the wrong drivers, and would like to spare others the pain :-). Thanks, ~David P.S. Some forum post said that the stable megatec drivers don't work 100% with the belkin UPS,

Hi, it'd be great if you could update the documentation on the website that some models of the Belkin -UNV series will only work with the megatec(_usb) drivers. I wasted a lot of time on trying to get it to work with the wrong drivers, and would like to spare others the pain :-). Thanks, ~David P.S. Some forum post said that the stable megatec drivers don't work 100% with the belkin UPS,

On Mon, Apr 27, 2015 at 2:13 PM, Joerg Schilling <Joerg.Schilling at fokus.fraunhofer.de> wrote: > Les Mikesell <lesmikesell at gmail.com> wrote: > > There was no court case, but VERITAS published a modifed version of gtar where > additional code was added by binary only libraries from VERITAS. The FSF did > never try to discuss this is public even though everybody did

https://bugzilla.mindrot.org/show_bug.cgi?id=2562 Bug ID: 2562 Summary: CanonicalizeHostname causes duplicate LocalForward attempts Product: Portable OpenSSH Version: 7.1p1 Hardware: ix86 OS: Mac OS X Status: NEW Severity: normal Priority: P5 Component: ssh

greetings, running Centos 4.1 i386 on a poweredge 1800, will be trying x86_64 tomorrow since apparently the processors are EM64. anyhow, I'm having issues with this unit producing segmentation faults on practically everything. this is not an issue just with Centos 4.x, but also RHEL 3. so I resorted to RH9, but had other issues with hardware drivers. Today, I installed OS and

Hi, I compiled drm & xf86-video-nouveau to test nouveau yesterday -- the X server couldn't start. Today, Telek pointed me to drm/linux-core/drm_pciids.h, where I added my card. This made nouveau detect my card, and the xerver started successfully. I didn't test further -- for example I didn't compile the mesa nouveau code to enable 3D. So what should I test ? Snark PS1:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi list, I just did my daily news scan and saw some screenshots that illustrate the press release [0] announcing the first collisions at the LHC. Those screenshots show windows and buttons that exactly match my CentOS GNOME Desktop [1]. AFAIK, SuSE/Novell has different skins, as has (Open)Solaris and AIX, for instance. So, has there anybody more

Hello, folks! I'm trying to use R as a graphics program, to make some pretty graphs that will go into prosper slideshows. I wrote this fragment, from the R manual, into a file demo.R: x=seq(-3,3,0.1) postscript("cm_test.eps", width = 4.0, height = 3.0, horizontal = FALSE, onefile = FALSE, paper = "special", family =

3a. What part of the documentation needs the most immediate attention? 3b. Will anyone come after me with an axe if I move the entire corpus to ASCIIDOC markup? http://www.methods.co.nz/asciidoc/ 3c. Why isn't the content of the website a branch in the repo? Can we fix things so it is? Hint: If the website becomes a repo branch, I'll reorganize and rewrite that for clarity, too. --

Hi Martin, Thanks for chiming in. Responses inline. On Fri, May 17, 2019 at 12:32 AM Martin Maechler <maechler at stat.math.ethz.ch> wrote: > >>>>> Gabriel Becker > >>>>> on Thu, 16 May 2019 15:47:57 -0700 writes: > > > Hi Hadley, > > Thanks for the counterpoint. Response below. > > > On Thu, May 16, 2019 at 1:59

Arnaud, my UPS arrived yesterday; thanks for your generosity. I'm using it to power the computer I'm typing on. This moves NUT up a few places on my priority list. In our last email exchange, I believe we agreed on a couple of major points. I want to confirm these before I start modifying the documentation heavily. 1. asciidoc is a good master format for the in-tree documentation. 2.

OK Eric, Den Tuesday 22 May 2007 08.56.08 skrev Eric S. Raymond: > Kjell Claesson <kjell.claesson at epost.tidanet.se>: > > Or install the udev rules and replug the ups. > > Did that. Manual startup of the driver now works without -u root, > indicating (I think) that the udev rools are doing their job. This >

2. Recommendations? My use case is pretty typical. I have one Linux machine I want to protect, automated shutown is desirable, blackouts longer than a hour are very rare at my location (the last one I can remember was in 1993), brownouts are very rare and mild, but summer thunderstorms are common and can be severe. I'm a good match for your typical consmer-grade UPS. 2a. In 2009, what do

Hallo all, euphoria with cheese, the project i working on, i needed to make decision about codecs and containers we use. I'm clearly not expert in this. After the euphoria about vp8/webm going slowly to the end, i see advantages what theora has against vp8. Seems like theora perform better on LoEnd hardware. Even x264 with good optimisation work not really good on slow Athom. My question to

I appreciate the well-thought-out comments. To your first point, I am not sure what "glattering" means precisely (a Google search revealed nothing useful), but I assume it means something to the effect of overfilling the main namespace with too many names. Per Norm Matloff's counterpoint in The Art of R Programming regarding this issue, this is mostly avoided by well-defined,

My UPS died two nights ago. From the symptoms, including the fact that the event took the motherboard of my main machine with it and the unreasonable amount of heat the UPS was generating immediately after, I believe this was a genuine fried-brains failure of the control electronics, not a mere battery death. The old UPS (a Belkin FVC1200) has been packed off to a recycler, and the motherboard