-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
documentation should say "do not put spaces in your home directory" #134
Comments
This is weird given it's supposedly init'ing in Is there any more of a trace where that error comes from / what script? |
Kind of; unfortunately, I can't redirect to a file, or I get a different error, but here's the amount I could copy from the backlog: https://gist.github.com/strega-nil/3fbd34423486a1073d6c5d87044940ca |
@strega-nil If you run |
I had the latest version from npm. Unfortunately, I just reinstalled windows, and my home directory no longer contains a space; I'll have to add a new user that does have a space in the home directory for future debugging. |
This topic came up today at the Electron Summit when discussing build-tools, and the consensus was that the edge cases that come from this extend into gn and may be outside of the scope of this repo to fix. So we're probably not going to fix this, but we should add a warning somewhere e.g. in the README |
e init
fails on windows when there are spaces in your home directory
The text was updated successfully, but these errors were encountered: