Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Warn the user when in a path that contains special characters #4966
There are a number of things, namely on Windows, where any non-UTF-8 character (and sometimes even non-alpnum characters) cause things to fail.
For gem installations that require compiling native extensions, any non-alphnum character will cause the build to fail - that means paths with spaces (like
Similarly, there are known issues in VirtualBox where non-UTF-8 characters in paths cause strange things to happen (#2113).
Given the breadth, span, and nature of these issues, I do not think it is possible to "fix" Vagrant. Instead, I propose we add a function early in Vagrant's initialization stage that sanity checks important paths and prints a helpful warning message (perhaps linking to more verbose documentation) when those paths contain "invalid" characters. Namely:
referenced this issue
Dec 13, 2014
In my environment, non-ASCII home (
to here, and it worked.
May be relevant to current code page.
Ah, I was getting confused between
<SystemProperties defaultMachineFolder="C:\Users\健吾\VirtualBox VMs" defaultHardDiskFormat="VDI" VRDEAuthLibrary="VBoxAuth" webServiceAuthLibrary="VBoxAuth" LogHistoryCount="3" exclusiveHwVirt="false"/>
<SystemProperties defaultMachineFolder="C:\VMs" defaultHardDiskFormat="VDI" VRDEAuthLibrary="VBoxAuth" webServiceAuthLibrary="VBoxAuth" LogHistoryCount="3" exclusiveHwVirt="false"/>
I discovered a method to "solve" this problem if someone doesn't want to change the real path to
MKLINK /J Link Target
Take this for an example:
MKLINK /J C:\Devs\links\i C:\Users\宁
You can place the link wherever you like ( a path that does not contain non-ASCII encoding characters ), then add
What's more, I think
Hope this will help