Skip to content

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

Closed
2 tasks done
andyleejordan opened this issue Jun 28, 2022 · 6 comments · Fixed by #4090
Closed
2 tasks done

RFC: Rename of the extension's Integrated Console #4053

andyleejordan opened this issue Jun 28, 2022 · 6 comments · Fixed by #4090
Assignees
Labels
Area-Extension Terminal Issue-Enhancement A feature request (enhancement).

Comments

@andyleejordan
Copy link
Member

Prerequisites

  • I have written a descriptive issue title.
  • I have searched all issues to ensure it has not already been reported.

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!

@andyleejordan andyleejordan added the Issue-Enhancement A feature request (enhancement). label Jun 28, 2022
@ghost ghost added the Needs: Triage Maintainer attention needed! label Jun 28, 2022
@andyleejordan
Copy link
Member Author

Made an issue @SydneyhSmith!

@panekj
Copy link

panekj commented Jun 28, 2022

PSEditorServices console?

@dragonwolf83
Copy link

dragonwolf83 commented Jun 29, 2022

Some ideas off top of my head

  • PowerShell Editor
  • PowerShell Editor Services
  • PowerShell Extension
  • PowerShell ISE

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:

  • PowerShell Editor Console
  • PowerShell Editor Services Console
  • PowerShell Extension Console

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?

@JustinGrote
Copy link
Collaborator

PowerShell Extension Console or just PowerShell Extension is the best I've seen, it clearly communicates to the user the purpose, they don't need to know the details about PSES. I am leaning towards the latter because Console is already implicit as its in the terminal area.

@andyleejordan
Copy link
Member Author

Wow, it's so simple...I really like PowerShell Extension as the label on the terminal too. And then in documentation we can refer to it as the PowerShell Extension Terminal

@SeeminglyScience
Copy link
Collaborator

How about "The right one" so when troubleshooting we can say "are you sure you're using the right one?"

jk I also like PowerShell Extension

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Extension Terminal Issue-Enhancement A feature request (enhancement).
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

6 participants