Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Show all profiles/shells in 'Open in Terminal' context menu #14597

Closed
tusharsnx opened this issue Dec 23, 2022 · 2 comments
Closed

Show all profiles/shells in 'Open in Terminal' context menu #14597

tusharsnx opened this issue Dec 23, 2022 · 2 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@tusharsnx
Copy link
Contributor

tusharsnx commented Dec 23, 2022 •
edited
Loading

Description of the new feature/enhancement

'Open in Terminal' should show all available profiles/shells using flyout. It only opens the default profile set in the Windows Terminal currently, and user has no way to choose between other profiles/shells from the context menu.

Proposed technical implementation details (optional)

'New'

Screenshot_20221223_114519

'Open in Terminal'

Screenshot_20221223_114535

As shown on the screenshot, adding a secondary flyout like one on the 'New' option to let the user choose which terminal shell they want to open 'here' will give additional flexibility while using the context menu.
A thing to note here is that opening the default terminal from the context menu might take two clicks instead of just one but IMO it's worth it.
@tusharsnx tusharsnx added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Dec 23, 2022
@ghost ghost added Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Dec 23, 2022
@zadjii-msft
Copy link
Member

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #6111 for more discussion.

/dup #6111

@ghost
Copy link

ghost commented Jan 3, 2023

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Jan 3, 2023
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jan 3, 2023
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zadjii-msft @tusharsnx