-
Notifications
You must be signed in to change notification settings - Fork 511
Restarting PowerShell session doesn't retain PowerShell Core selection #807
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
Same thing happens when you switch to built-in x86. :-( |
Weird... Not sure how that broke! |
In other words, I don't think your changes caused it :) |
It's like you're a mind reader. :-p But that doesn't necessarily mean my change didn't break something. I hope not. |
I'm pretty sure it didn't, the more likely culprit is the changes around adoption of the newer vscode-languageclient library, that broke other stuff too. |
Ok, I'm wondering if this ever worked... https://github.com/PowerShell/vscode-powershell/blob/master/src/session.ts#L713 |
Guess that should be passing in the current sessionConfiguration, eh? |
Yep. I'm about to submit a PR |
This change fixes PowerShell#807 which states that restarting the current PowerShell session using the "Restart Current Session" command doesn't retain the current session configuration if the user previously switched their configuration using the session menu. The fix is to change the call to restartSession to use the current session configuration when this command is invoked.
This change fixes #807 which states that restarting the current PowerShell session using the "Restart Current Session" command doesn't retain the current session configuration if the user previously switched their configuration using the session menu. The fix is to change the call to restartSession to use the current session configuration when this command is invoked.
This change fixes one remaining issue with restarting PowerShell sessions that were started using the session menu.
For some reason when I select one of the new PowerShell Core entries from the session menu, let the new session load, then try to reload it, it goes back to selecting the built-in Windows PowerShell install. I would expect it to reload the session that was selected most recently.
The text was updated successfully, but these errors were encountered: