Re: [Rd] Bug: Issues on Windows with SFN disabled

> > This is actually a pretty big peeve of mine. "Program Files" is where > programs are *supposed* to reside on Windows. > PS -- Microsoft's reasoning is explained in "Why do program files go into the Program Files directory?" https://blogs.msdn.microsoft.com/oldnewthing/20120307-00/?p=8153

Re: [Rd] Bug: Issues on Windows with SFN disabled

Does Windows allow creating a symlink to "C:/Program Files"? If so, R could install into the conventional Windows location, but use the symlink for all its access, yes? Windows 10 command = mklink On Fri, Dec 8, 2017 at 11:14 AM, Zach Bjornson wrote: > Thanks for fixing

Re: [Rd] Bug: Issues on Windows with SFN disabled

Thanks for fixing this! For what it's worth, the Windows installers for other programming language runtimes often install outside of Program Files, so at least there is 'prior art' to motivate having R install directly into the root of the home drive: This is actually a pretty big peeve of

Re: [Rd] Bug: Issues on Windows with SFN disabled

On 8 December 2017 at 08:52, Kevin Ushey wrote: | For what it's worth, the Windows installers for other programming | language runtimes often install outside of Program Files, so at least | there is 'prior art' to motivate having R install directly into the | root of the home drive: | | -

Re: [Rd] Bug: Issues on Windows with SFN disabled

For what it's worth, the Windows installers for other programming language runtimes often install outside of Program Files, so at least there is 'prior art' to motivate having R install directly into the root of the home drive: - ActiveState Perl installs directly C:/Perl; - Python

Re: [Rd] Bug: Issues on Windows with SFN disabled

On 12/07/2017 06:15 PM, Dirk Eddelbuettel wrote: On 7 December 2017 at 17:56, Tomas Kalibera wrote: | | An update on this. Writing R Extensions does not recommend to have a | space character in R_HOME. This means that on Windows one either should | have SFN enabled (which is still the common

Re: [Rd] Bug: Issues on Windows with SFN disabled

On 7 December 2017 at 17:56, Tomas Kalibera wrote: | | An update on this. Writing R Extensions does not recommend to have a | space character in R_HOME. This means that on Windows one either should | have SFN enabled (which is still the common case), or install into a | directory that does

Re: [Rd] Bug: Issues on Windows with SFN disabled

An update on this. Writing R Extensions does not recommend to have a space character in R_HOME. This means that on Windows one either should have SFN enabled (which is still the common case), or install into a directory that does not have a space in its name (so specifically not into

Re: [Rd] Bug: Issues on Windows with SFN disabled

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

Re: [Rd] Bug: Issues on Windows with SFN disabled

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

[Rd] Bug: Issues on Windows with SFN disabled

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 -