From tomas.kalibera at gmail.com  Tue Oct 17 10:37:28 2017
From: tomas.kalibera at gmail.com (Tomas Kalibera)
Date: Tue, 17 Oct 2017 10:37:28 +0200
Subject: [Rd] Bug: Issues on Windows with SFN disabled
In-Reply-To: <CAD7tZLXB=73wY9tqLmYhTXyBB9DMO1WZXGz3U9pHz9KgEX4K=Q@mail.gmail.com>
References: <CAD7tZLXB=73wY9tqLmYhTXyBB9DMO1WZXGz3U9pHz9KgEX4K=Q@mail.gmail.com>
Message-ID: <34ec506d-bec1-544f-9067-2109bd0db1e5@gmail.com>

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



[Rd] Bug: Issues on Windows with SFN disabled
Tomas Kalibera