Sidebar for Profiles #18974

Closed
opened 2026-01-31 06:30:07 +00:00 by claunia · 7 comments
Owner

Originally created by @MXMLN-sec on GitHub (Nov 28, 2022).

Description of the new feature/enhancement

I currently have about 30 profiles that I need again and again to establish connections to servers. Selecting from the drop-down list becomes very confusing over time, which is why I would find a sidebar very practical.
Similar to other multi-terminal programmes, you can then establish a new connection from the sidebar by double-clicking on the profile.

Proposed technical implementation details (optional)

Originally created by @MXMLN-sec on GitHub (Nov 28, 2022). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement I currently have about 30 profiles that I need again and again to establish connections to servers. Selecting from the drop-down list becomes very confusing over time, which is why I would find a sidebar very practical. Similar to other multi-terminal programmes, you can then establish a new connection from the sidebar by double-clicking on the profile. <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> # Proposed technical implementation details (optional) <!-- A clear and concise description of what you want to happen. -->
Author
Owner

@237dmitry commented on GitHub (Nov 28, 2022):

Selecting from the drop-down list becomes very confusing over time, which is why I would find a sidebar very practical.

I don't mind the panel if it's not always visible. Do you launch every profile manually every time? Launch all at once from powershell tab.


# Check the path to settings.json. This one is for WT Preview
 
$json = "$env:LocalAppData\Packages\Microsoft.WindowsTerminalPreview_8wekyb3d8bbwe\LocalState\settings.json"

(Get-Content $json | ConvertFrom-Json).profiles.list |
    Where-Object   { (-not $_.hidden) -and ($_.guid -ne $env:WT_PROFILE_ID) } |
    Foreach-Object { wt --window 0 new-tab --profile $_.name }

@237dmitry commented on GitHub (Nov 28, 2022): > Selecting from the drop-down list becomes very confusing over time, which is why I would find a sidebar very practical. I don't mind the panel if it's not always visible. Do you launch every profile manually every time? Launch all at once from powershell tab. ```powershell # Check the path to settings.json. This one is for WT Preview $json = "$env:LocalAppData\Packages\Microsoft.WindowsTerminalPreview_8wekyb3d8bbwe\LocalState\settings.json" (Get-Content $json | ConvertFrom-Json).profiles.list | Where-Object { (-not $_.hidden) -and ($_.guid -ne $env:WT_PROFILE_ID) } | Foreach-Object { wt --window 0 new-tab --profile $_.name } ```
Author
Owner

@zadjii-msft commented on GitHub (Nov 28, 2022):

Interesting idea. There's a couple items on the backlog that might be a bit easier to implement

  • #1571 (customize the dropdown to be easier to navigate)
  • #3586 (Yea, the title says "pane", but a tab just starts with a single pane 😉)

or alternatively, using the command palette to search for which profile to open
command-palette-gh-14453

Would any of that work for you/?

@zadjii-msft commented on GitHub (Nov 28, 2022): Interesting idea. There's a couple items on the backlog that might be a bit easier to implement * #1571 (customize the dropdown to be easier to navigate) * #3586 (Yea, the title says "pane", but a tab just starts with a single pane 😉) or alternatively, using the command palette to search for which profile to open ![command-palette-gh-14453](https://user-images.githubusercontent.com/18356694/204284939-e08050e1-0916-4408-9d1f-cfbcbf4f71f4.gif) Would any of that work for you/?
Author
Owner

@ghost commented on GitHub (Dec 2, 2022):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Dec 2, 2022): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
Author
Owner

@MXMLN-sec commented on GitHub (Dec 5, 2022):

Selecting from the drop-down list becomes very confusing over time, which is why I would find a sidebar very practical.

I don't mind the panel if it's not always visible. Do you launch every profile manually every time? Launch all at once from powershell tab.




# Check the path to settings.json. This one is for WT Preview

 

$json = "$env:LocalAppData\Packages\Microsoft.WindowsTerminalPreview_8wekyb3d8bbwe\LocalState\settings.json"



(Get-Content $json | ConvertFrom-Json).profiles.list |

    Where-Object   { (-not $_.hidden) -and ($_.guid -ne $env:WT_PROFILE_ID) } |

    Foreach-Object { wt --window 0 new-tab --profile $_.name }



Neat idea. But I need to select the server I need to connect to depending on the task I need to perform. So unfortunately I can't automate this. But probably helpful for the future!

@MXMLN-sec commented on GitHub (Dec 5, 2022): > > Selecting from the drop-down list becomes very confusing over time, which is why I would find a sidebar very practical. > > > > I don't mind the panel if it's not always visible. Do you launch every profile manually every time? Launch all at once from powershell tab. > > > > ```powershell > > > > # Check the path to settings.json. This one is for WT Preview > > > > $json = "$env:LocalAppData\Packages\Microsoft.WindowsTerminalPreview_8wekyb3d8bbwe\LocalState\settings.json" > > > > (Get-Content $json | ConvertFrom-Json).profiles.list | > > Where-Object { (-not $_.hidden) -and ($_.guid -ne $env:WT_PROFILE_ID) } | > > Foreach-Object { wt --window 0 new-tab --profile $_.name } > > > > ``` Neat idea. But I need to select the server I need to connect to depending on the task I need to perform. So unfortunately I can't automate this. But probably helpful for the future!
Author
Owner

@MXMLN-sec commented on GitHub (Dec 5, 2022):

Interesting idea. There's a couple items on the backlog that might be a bit easier to implement

  • #1571 (customize the dropdown to be easier to navigate)

  • #3586 (Yea, the title says "pane", but a tab just starts with a single pane 😉)

or alternatively, using the command palette to search for which profile to open

command-palette-gh-14453

Would any of that work for you/?

Nice idea with the drop down customisation! I will try it.

The search will mit not always work for me since I don't have all the server names right in the top of my head. Which brings me to another idea: my suggested sidebar could be extended with folders to organise entries for example powershell scripts, customer a, customer b, and so on.

@MXMLN-sec commented on GitHub (Dec 5, 2022): > Interesting idea. There's a couple items on the backlog that might be a bit easier to implement > > > > * #1571 (customize the dropdown to be easier to navigate) > > * #3586 (Yea, the title says "pane", but a tab just starts with a single pane 😉) > > > > or alternatively, using the command palette to search for which profile to open > > ![command-palette-gh-14453](https://user-images.githubusercontent.com/18356694/204284939-e08050e1-0916-4408-9d1f-cfbcbf4f71f4.gif) > > > > > > Would any of that work for you/? Nice idea with the drop down customisation! I will try it. The search will mit not always work for me since I don't have all the server names right in the top of my head. Which brings me to another idea: my suggested sidebar could be extended with folders to organise entries for example powershell scripts, customer a, customer b, and so on.
Author
Owner

@zadjii-msft commented on GitHub (Dec 5, 2022):

The search will mit not always work for me since I don't have all the server names right in the top of my head. Which brings me to another idea: my suggested sidebar could be extended with folders to organise entries for example powershell scripts, customer a, customer b, and so on

You can actually also customize the entries in the Command Palette however you'd like! This doc has a trivial example with combining entries under a "Change font size..." entry, but you could easily add newTab actions all nested under each customer if you wanted

@zadjii-msft commented on GitHub (Dec 5, 2022): > The search will mit not always work for me since I don't have all the server names right in the top of my head. Which brings me to another idea: my suggested sidebar could be extended with folders to organise entries for example powershell scripts, customer a, customer b, and so on You can actually also customize the entries in the Command Palette however you'd like! [This doc](https://learn.microsoft.com/en-us/windows/terminal/command-palette#nested-commands) has a trivial example with combining entries under a "Change font size..." entry, but you could easily add `newTab` actions all nested under each customer if you wanted
Author
Owner

@ghost commented on GitHub (Dec 9, 2022):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Dec 9, 2022): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#18974