-
Notifications
You must be signed in to change notification settings - Fork 511
RFC: Rename of the extension's Integrated Console #4053
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
Made an issue @SydneyhSmith! |
|
Some ideas off top of my head
Do we need to have Console in the name, it is implied since it is in a Terminal dropdown? With it included it is longer:
Would it make sense to have PowerShell name be dynamic based on if its pwsh version or powershell? For example, pwsh editor when its pwsh. Or does that make it more confusing for people? |
|
Wow, it's so simple...I really like |
How about "The right one" so when troubleshooting we can say "are you sure you're using the right one?" jk I also like |
Prerequisites
Summary
I am proposing that we rename the PowerShell Extension's "Integrated Console" (often abbreviated PSIC) to...something else, because VS Code already uses the term "integrated" twice, once for the "Integrated Terminals" and again for their "Shell Integration" feature. So if we have to talk about the latter, it goes something like this: "VS Code's Shell Integration doesn't work in the (PowerShell Extension's) Integrated Console despite it being a (VS Code) Integrated Terminal."
Proposed Design
Maybe just "Extension Terminal" or "The Extension's Terminal." We need to workshop this. Suggestions solicited!
The text was updated successfully, but these errors were encountered: