-
Notifications
You must be signed in to change notification settings - Fork 520
Remove -NonInteractive from PowerShell startup sequence
#3847
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
Conversation
This command-line flag sets a low-level configuration within PowerShell that prevents Windows PowerShell from using interactive parameters in scripts (such as in `Get-Credential`). It does not appear to be necessary for us to use this flag, so we're going to test without it.
b1c1f0b to
2396f7c
Compare
@SeeminglyScience On PowerShell 5.1 and 7.2.1, the previous bug where the wrong PSReadLine was loaded does not appear to be recurring with this PR. They both loaded the module from the extension path, despite other versions of PSReadLine being available (and loaded in the standalone console).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ahh that's right. -Command/-File should do the same as long as -NoExit isn't present. LGTM!
This command-line flag sets a low-level configuration within PowerShell
that prevents Windows PowerShell from using interactive parameters in
scripts (such as in
Get-Credential). It does not appear to benecessary for us to use this flag, so we're going to test without it.
Fixes #3820.