1. I know there is not such a thing; that why I said "mimic" and "the
same place" ("***/R/bin" instead of "***/R/R-x.x.x/bin").
2. Yes, I never mess with the PATH variable under *nix, because R is
installed to /usr/local/bin/ (or /usr/bin/) *by default*, which is
already in the PATH variable. Othe
First, you are still able to install multiple versions of R to any
places that you want -- I was suggesting a default place to install R
under Windows. If you remember the process of installing R under
Windows, there is a step in which you can choose where to install R.
Second, to modify the PATH
Yihui Xie-2 wrote:
>
> Hi,
>
> I guess this issue must have been brought forward long time ago, but I
> still hope you can consider under Windows (during installation):
>
> 1. put R's bin path in the PATH variable of the system so that we can
> use the commands "R" and "Rscript" more easily;
>
There are plenty of good reasons for non-developers to run different
versions of R. For instance, I care a lot about reproducibility. With
every new release of R, lots of things change. With every new release
of the packages I use, lots of things change. All of my analyses are
performed usin
On May 4, 2011, at 12:00 PM, Yihui Xie wrote:
> My suggestion was to mimic *nix systems: put the executable binaries in the
> same place *by default* (e.g. /usr/bin/ or /usr/local/bin).
Except that there is not such thing on Windows! The closest to that is the
"system" folder which is off limit
My suggestion was to mimic *nix systems: put the executable binaries
in the same place *by default* (e.g. /usr/bin/ or /usr/local/bin). Why
isn't the default bin path for R under *nix something like
/usr/bin/R-2.13.0/? If the users want to install multiple versions,
they still have the choice to in
In terms of a personal use, that is absolutely fine. From the
perspective of a developer, you cannot stop a user from upgrading to
newer versions. Perhaps it is a matter of personal taste; I'm worried
more about adapting to latest versions than maintaining old versions.
If the new versions works fi
>> Subject: Re: [Rd] Wishlist: write R's bin path to the PATH variable and
> remove
>> the version string in the installation dir under Windows
>>
>> [snip]
>> I personally keep about half a dozen back versions of R for the reasons
>> others have menti
On Wed, May 4, 2011 at 11:15 AM, Yihui Xie wrote:
> If I am already able to open R, there is no need to post the request
> here. I want to be able to run R without knowing where it is from
> another software package. Your batch files fit in this purpose, and
> the only problem is it is a little bi
If I am already able to open R, there is no need to post the request
here. I want to be able to run R without knowing where it is from
another software package. Your batch files fit in this purpose, and
the only problem is it is a little bit slower since it takes time to
look for R in the system vi
> -Original Message-
> From: r-devel-boun...@r-project.org [mailto:r-devel-bounces@r-
> project.org] On Behalf Of Gabor Grothendieck
> Sent: May-04-11 10:35 AM
> To: Duncan Murdoch
> Cc: R-devel
> Subject: Re: [Rd] Wishlist: write R's bin path to the PATH variabl
On Wed, May 4, 2011 at 8:11 AM, Duncan Murdoch wrote:
> On 11-05-03 11:25 PM, Yihui Xie wrote:
>>
>> 1. "Few Windows users use these commands" does not imply they are not
>> useful, and I have no idea how many Windows users really use them. How
>> do you run "R CMD build" when you build R packages
On 11-05-03 11:25 PM, Yihui Xie wrote:
1. "Few Windows users use these commands" does not imply they are not
useful, and I have no idea how many Windows users really use them. How
do you run "R CMD build" when you build R packages under Windows? You
don't write "C:/Program Files/R/R-2.13.0/bin/i3
> Wincent
> on Wed, 4 May 2011 13:46:13 +0800 writes:
> I also prefer to keep the old versions. Sometimes, I have
> spent time to set up the system with older version and
> don't want to update to the latest (e.g. the new RGtk2
> needs updated GTk2 as well) because t
I also prefer to keep the old versions.
Sometimes, I have spent time to set up the system with older version
and don't want to update to the latest (e.g. the new RGtk2 needs
updated GTk2 as well) because the older still works and I don't need
the new features.
Regards
Ronggui
On 4 May 2011 13:26
On Wed, May 4, 2011 at 1:04 AM, Yihui Xie wrote:
> Thanks! But I'm sorry this is not what I wanted. I just hope we can
> call R as a command like we do under *nix -- this will make it easier
> for *other* software packages to find R.
You asked for an R program that gives the ability to run R.exe,
On Wed, May 4, 2011 at 3:25 PM, Yihui Xie wrote:
> 1. "Few Windows users use these commands" does not imply they are not
> useful, and I have no idea how many Windows users really use them. How
> do you run "R CMD build" when you build R packages under Windows? You
> don't write "C:/Program Files/
Thanks! But I'm sorry this is not what I wanted. I just hope we can
call R as a command like we do under *nix -- this will make it easier
for *other* software packages to find R.
BTW, for the cmd package: if we were "evil" enough, we can directly
execute this in R to permanently set the PATH varia
On Tue, May 3, 2011 at 7:44 PM, Yihui Xie wrote:
> Hi,
>
> I guess this issue must have been brought forward long time ago, but I
> still hope you can consider under Windows (during installation):
>
> 1. put R's bin path in the PATH variable of the system so that we can
> use the commands "R" and
Well, it seems I still have not make myself clear enough: I myself do
not have any questions here -- I know all the solutions, and I just do
not want to (1) explain to people again and again what is the PATH
variable under Windows (2) have to think where is R when I want to run
R as a command.
So
On May 3, 2011, at 11:25 PM, Yihui Xie wrote:
> 1. "Few Windows users use these commands" does not imply they are not
> useful, and I have no idea how many Windows users really use them. How
> do you run "R CMD build" when you build R packages under Windows? You
> don't write "C:/Program Files/R/
1. "Few Windows users use these commands" does not imply they are not
useful, and I have no idea how many Windows users really use them. How
do you run "R CMD build" when you build R packages under Windows? You
don't write "C:/Program Files/R/R-2.13.0/bin/i386/R.exe CMD build", do
you?
I think the
1. I understand the efforts in those batch files, but my philosophy is
to let the users go through as less steps as they can. Since it is
possible to do it in R directly, I prefer not to download those batch
files and execute commands like R.bat CMD build or Rscript.bat file.R.
This requires extra
On 03/05/2011 7:44 PM, Yihui Xie wrote:
Hi,
I guess this issue must have been brought forward long time ago, but I
still hope you can consider under Windows (during installation):
1. put R's bin path in the PATH variable of the system so that we can
use the commands "R" and "Rscript" more easil
On Tue, May 3, 2011 at 7:44 PM, Yihui Xie wrote:
> Hi,
>
> I guess this issue must have been brought forward long time ago, but I
> still hope you can consider under Windows (during installation):
>
> 1. put R's bin path in the PATH variable of the system so that we can
> use the commands "R" and
Hi,
I guess this issue must have been brought forward long time ago, but I
still hope you can consider under Windows (during installation):
1. put R's bin path in the PATH variable of the system so that we can
use the commands "R" and "Rscript" more easily;
2. remove the version string like R-2.
26 matches
Mail list logo
