-
Notifications
You must be signed in to change notification settings - Fork 18
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
Windows: Starting client failed #52
Comments
It cannot work properly in system PATH. red/red#543 |
I think this setting (red.redPath) is outdated in the latest plugin. Document needs to be updated. Please try the following command:
|
No, that just results in a different failure mode:
Accompanying popup:
|
@HunterZ Did you use the automated builds version of Red? 0.6.4 is way too outdated. |
I used chocolatey to install, as mentioned on the official download page. I didn't understand the comment on the extension about needing a newer build, so that's probably the problem. What a mess; I guess I'll check back later, as I'm not up for messing with manually installing cutting edge builds of things at the moment. |
You don't need to install Red. Just download it and use it directly. ;-) |
Getting the following error on Windows 10:
It's completely ignoring my
red.redPath
setting. I've tried the following values:It's almost like it's looking in a hard-coded path and ignoring the
red.redPath
setting.Also, red.exe is in my system PATH, so why do I even need to tell VSCode where to find it?
The text was updated successfully, but these errors were encountered: