Hello, R appears to assume that Windows drives have short file names (SFN, 8.3) enabled; for example, that "C:/Program Files/..." is addressable as "C:/Progra~1/...". Newer versions of Windows have SFN disabled on non-OS drives, however. This means that if you install R on a non-OS drive, you - can't start R.exe from the command line. - consequently, anything that attempts to spawn a new R process also fails. This includes a lot of the commands from the popular devtools package. More discussion and background: https://github.com/hadley/devtools/issues/1514 I don't have access to bugzilla to file this there. Thanks and best, Zach [[alternative HTML version deleted]]
Hi Zach,
thanks for the report, I can reproduce the problem and confirm it is a
bug in R and will be fixed.
Hopefully it only impacts few users now. The workaround is to create the
short name for the directory where R is installed, using "fsutil file
setshortname" (for all elements of the path that contain space in their
name). One can revert this by setting the shortname to an empty string
(""). At least for the latter one may need to boot in safe mode.
Best
Tomas
On 09/17/2017 08:23 PM, Zach Bjornson wrote:> Hello,
>
> R appears to assume that Windows drives have short file names (SFN, 8.3)
> enabled; for example, that "C:/Program Files/..." is addressable
as
> "C:/Progra~1/...". Newer versions of Windows have SFN disabled on
non-OS
> drives, however.
>
> This means that if you install R on a non-OS drive, you
> - can't start R.exe from the command line.
> - consequently, anything that attempts to spawn a new R process also fails.
> This includes a lot of the commands from the popular devtools package. More
> discussion and background: https://github.com/hadley/devtools/issues/1514
>
> I don't have access to bugzilla to file this there.
>
> Thanks and best,
> Zach
>
> [[alternative HTML version deleted]]
>
> ______________________________________________
> R-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel
This has now been mostly fixed in R-devel. What remains to be resolved is that some packages with custom make files cannot be installed from source (when R is installed into a directory with space in its name and short file names are not available) Tomas On 10/17/2017 10:37 AM, Tomas Kalibera wrote:> Hi Zach, > > thanks for the report, I can reproduce the problem and confirm it is a > bug in R and will be fixed. > > Hopefully it only impacts few users now. The workaround is to create > the short name for the directory where R is installed, using "fsutil > file setshortname" (for all elements of the path that contain space in > their name). One can revert this by setting the shortname to an empty > string (""). At least for the latter one may need to boot in safe mode. > > Best > Tomas > > > On 09/17/2017 08:23 PM, Zach Bjornson wrote: >> Hello, >> >> R appears to assume that Windows drives have short file names (SFN, 8.3) >> enabled; for example, that "C:/Program Files/..." is addressable as >> "C:/Progra~1/...". Newer versions of Windows have SFN disabled on non-OS >> drives, however. >> >> This means that if you install R on a non-OS drive, you >> - can't start R.exe from the command line. >> - consequently, anything that attempts to spawn a new R process also >> fails. >> This includes a lot of the commands from the popular devtools >> package. More >> discussion and background: >> https://github.com/hadley/devtools/issues/1514 >> >> I don't have access to bugzilla to file this there. >> >> Thanks and best, >> Zach >> >> ????[[alternative HTML version deleted]] >> >> ______________________________________________ >> R-devel at r-project.org mailing list >> https://stat.ethz.ch/mailman/listinfo/r-devel > >