Here's the short answer: Whatever you used to do should still work.
I started this thread, not knowing that it was going to get sucked into
a whirlpool on the fringes of an operating system religious war. My
sincerest apologies to everyone who has gotten confused as a consequence.
I only ra
Well, color me confused as heck. I've upgraded to R 3.0 so that I can bring
my packages up to date, but the instructions surrounding Rtools30 are not a
model of clarity.
On Sun, Apr 21, 2013 at 4:04 PM, Gabor Grothendieck wrote:
> On Sun, Apr 21, 2013 at 6:17 PM, Henrik Bengtsson
> wrote:
> >
On Sun, Apr 21, 2013 at 6:17 PM, Henrik Bengtsson wrote:
> I (as well) keep a specific Rsetup.bat file for launching Windows
> cmd.exe with the proper PATH etc setup for build R packages etc. It's
> only after this thread I gave it a second thought; you can indeed
> temporarily set the PATH via ~
> PS. Hadley, is this what you meant when you wrote "Better solutions
> (e.g. Rstudio and devtools) temporarily set the path on when you're
> calling R CMD *.", or those approaches are only when you call 'R CMD'
> from the R prompt? I believe the latter, but I just want to make sure
> I didn't mis
I (as well) keep a specific Rsetup.bat file for launching Windows
cmd.exe with the proper PATH etc setup for build R packages etc. It's
only after this thread I gave it a second thought; you can indeed
temporarily set the PATH via ~/.Rprofile or ~/.Renviron, which *are*
processed at the very begin
On 4/21/2013 1:47 PM, Uwe Ligges wrote:
>> Since vignettes are re-built from sources and then installed into
>> inst/doc, I don't see why
>> PDF compaction cannot be run as part of the build process. That is, if
>> R CMD check --as-cran detects a problem, shouldn't there be some
>> option for
>> R
On Sun, Apr 21, 2013 at 1:48 PM, Prof J C Nash (U30A) wrote:
>
> While as a Linux user who has not so far been banished to Winland I have not
> experienced this problem, it seems to be the type of issue where a "how to",
> for example, on the R Wiki, would be helpful. Moreover, surely this is a
>
On Sun, Apr 21, 2013 at 12:57 PM, Hadley Wickham wrote:
Because it can conflict with other Windows software unless you add a
layer over it. What other popular software that runs on Windows has
these problems? I can't think of any. The closest I can come up with
was that for
While as a Linux user who has not so far been banished to Winland I have
not experienced this problem, it seems to be the type of issue where a
"how to", for example, on the R Wiki, would be helpful. Moreover, surely
this is a name conflict on different platforms, so possibly a list of
these
On 21.04.2013 19:28, Michael Friendly wrote:
[Env: OS: Win Xp; R 2.15.2; IDE: eclipse/StatET]
Each time I update my heplots package, I get warnings from R CMD check
on R-Forge,
* checking sizes of PDF files under ‘inst/doc’ ... WARNING
‘gs+qpdf’ made some significant size reductions:
[Env: OS: Win Xp; R 2.15.2; IDE: eclipse/StatET]
Each time I update my heplots package, I get warnings from R CMD check
on R-Forge,
* checking sizes of PDF files under ‘inst/doc’ ... WARNING
‘gs+qpdf’ made some significant size reductions:
compacted ‘HE-examples.pdf’ from 739Kb to 366Kb
>>> Because it can conflict with other Windows software unless you add a
>>> layer over it. What other popular software that runs on Windows has
>>> these problems? I can't think of any. The closest I can come up with
>>> was that for a short time after git was ported to Windows it would
>>> cha
On Sun, Apr 21, 2013 at 9:49 AM, Hadley Wickham wrote:
>> Because it can conflict with other Windows software unless you add a
>> layer over it. What other popular software that runs on Windows has
>> these problems? I can't think of any. The closest I can come up with
>> was that for a short t
> Because it can conflict with other Windows software unless you add a
> layer over it. What other popular software that runs on Windows has
> these problems? I can't think of any. The closest I can come up with
> was that for a short time after git was ported to Windows it would
> change the fo
On Sun, Apr 21, 2013 at 8:18 AM, Hadley Wickham wrote:
>> The problem is that if you don't just use the PC for running R but use
>> it to run other programs too then any program and that utilizes
>> Windows batch scripts making use of find.exe or sort.exe likely won't
>> work if Rtools is on your
> The problem is that if you don't just use the PC for running R but use
> it to run other programs too then any program and that utilizes
> Windows batch scripts making use of find.exe or sort.exe likely won't
> work if Rtools is on your path.
>
> The fact that devtools, batchfiles and Rcpp have w
16 matches
Mail list logo
