-
Notifications
You must be signed in to change notification settings - Fork 21
Custom PowerShell Editor Services path is reset if using on Linux or Mac #105
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
It is likely that you've been hit by a settings save issue. I think that before #89, validation of PowerShell executable on Linux was broken (and, while it should work, it is still clunky; further setting improvements are logged as #111). And there's a Rider issue nobody bothered to report separately: in case of settings save errors, Rider is unable to show the error message (because of how the settings UI is customized). So, you have an error, but you can't see it, and that's the problem. Anyway, in this case, I believe it should be fixed by #89. |
@ForNeVeR |
@ivanskorikov, the last message I see in the logs is:
Have you customized the PowerShell path? If not, then do you have it in |
Pwsh executable path was indeed not in the PATH variable for some reason. Everything works upon reinstalling Powershell, settings are saved correctly and I even get completion suggestions with custom PSES (unlike #104, which incidentally happens on Windows) |
STR:
File | Settings | Languages & Frameworks | PowerShell
and provide a custom path to PSES => Version of PSES correctly changes to whatever is provided.File | Settings | Languages & Frameworks | PowerShell
againActual result:
PSES version is reset to bundled v.1.10.1
Expected result:
Plugin still displays the custom path and custom PSES version
The text was updated successfully, but these errors were encountered: