-
Notifications
You must be signed in to change notification settings - Fork 8.5k
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
Comments
Wow have you ever got a lot of WSL distributions! |
and I cleaned some out to avoid "shocking" 😭 |
It would be nice to have groups that have a flyout menu. |
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! |
oh sorry for that, great it's already discussed, thanks a lot Mike 👍 |
@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: So yeah, it would definitely be great. I am liking Windows Terminal so far. |
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](https://user-images.githubusercontent.com/905874/74275501-46c19d80-4d14-11ea-9347-76a00bf89dd2.png)
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
The text was updated successfully, but these errors were encountered: