-
Notifications
You must be signed in to change notification settings - Fork 511
Extension is not working if windows username contains spaces #244
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
Comments
Ouch, I immediately see the issue. Sorry for the trouble! Will get this fixed in the next couple of days. |
The path to Start-EditorServices.ps1 needs to be enclosed with quotation marks:
|
Same issue... after about 2 hours of debugging i finally decided to check out the bugs section. Thanks for filing this, thanks for fixing this and thanks for the fix! |
Hey Andrew, sorry for the trouble, I'll definitely get this fixed soon! Working on fixes for an upcoming 0.7.1 update right now. |
This change fixes #244 which reports that the extension does not load when the user's username contains a space. This was caused by the script execution of Start-EditorServices.ps1 not being contained within quotes.
I just released an update to the extension, check it out and see if it resolve the issue for you! |
It works like a charm! Thank you! |
Excellent, thanks a lot for confirming! |
Installed extension today for the first time and it seems like I'm the only one who got spaces in windows account. :) Basically, EditorServices couldn't be started (log attached) and I guess debugger fails for the same reason. Added local account without spaces -- everything works.
1471546041-PowerShell.txt
The text was updated successfully, but these errors were encountered: