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.

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

[Menu] Shells sub-grouping #4535

Closed
nunix opened this issue Feb 11, 2020 · 7 comments
Closed

[Menu] Shells sub-grouping #4535

nunix opened this issue Feb 11, 2020 · 7 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

@nunix
Copy link

nunix commented Feb 11, 2020

Description of the new feature/enhancement

for some (crazy) fans of having several shells, the selection menu can become very long very fast (see picture below).

It might be nice to have a "sub-grouping" for the different shells, so the menu would remain more clean.
At first, it could even be the "discovered shells" that could all be in a sub-group, so we could customize them and bring them back to the main menu

today's example:
image

Proposed technical implementation details (optional)

The nearest solution that already exists, might be the browser favorites, with only 1 level deep to keep it simple.

The Corsair

@nunix nunix added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Feb 11, 2020
@ghost ghost added 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 Feb 11, 2020
@DHowett-MSFT
Copy link
Contributor

Wow have you ever got a lot of WSL distributions!

@nunix
Copy link
Author

nunix commented Feb 11, 2020

and I cleaned some out to avoid "shocking" 😭

@mdtauk
Copy link

mdtauk commented Feb 11, 2020

It would be nice to have groups that have a flyout menu.

@zadjii-msft
Copy link
Member

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

/dup #1571

@ghost
Copy link

ghost commented Feb 11, 2020

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 Feb 11, 2020
@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 Feb 11, 2020
@nunix
Copy link
Author

nunix commented Feb 11, 2020

oh sorry for that, great it's already discussed, thanks a lot Mike 👍

@bkraul
Copy link

bkraul commented May 29, 2020

@DHowett-MSFT this doesn't only apply to multiple WSL distributions. It could be that we only have one WSL distribution but have a number of SSH connections to remote servers. Right now, using solutions like cmder, we have something like this:
image

So yeah, it would definitely be great. I am liking Windows Terminal so far.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Development

No branches or pull requests

5 participants