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

Sidebar for Profiles #14453

Closed
MXMLN-sec opened this issue Nov 28, 2022 · 7 comments
Closed

Sidebar for Profiles #14453

MXMLN-sec opened this issue Nov 28, 2022 · 7 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something 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 No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity.

Comments

@MXMLN-sec
Copy link

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)

@MXMLN-sec MXMLN-sec added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Nov 28, 2022
@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 Nov 28, 2022
@237dmitry
Copy link

237dmitry commented 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 }

@zadjii-msft
Copy link
Member

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

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

Would any of that work for you/?

@ghost ghost added Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. labels Nov 28, 2022
@ghost
Copy link

ghost commented 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.

@MXMLN-sec
Copy link
Author

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!

@ghost ghost added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. labels Dec 5, 2022
@MXMLN-sec
Copy link
Author

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

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.

@zadjii-msft
Copy link
Member

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 zadjii-msft added Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something and removed Needs-Attention The core contributors need to come back around and look at this ASAP. labels Dec 5, 2022
@ghost ghost added the No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. label Dec 9, 2022
@ghost
Copy link

ghost commented 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 ghost closed this as completed Dec 12, 2022
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. Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something 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 No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity.
Projects
None yet
Development

No branches or pull requests

3 participants