starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

custom profiles don't scale #10801

New Issue
Closed
opened 2026-01-31 02:30:40 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 02:30:40 +00:00
Owner
Copy Link

Originally created by @cadayton on GitHub (Sep 27, 2020).

I have hundreds of potential ssh sessions and I don't want to create 100s of custom profiles for each instance. It would helpful if parameterized custom profiles was supported. Also, looking forward to when new-tab can actually open a new tab rather than a new window.

Today, I do the following with ConEMU. Define a PowerShell alias 'ldp' (load putty) that does the following.
putty.exe -new_console -load $hostname

In a ConEMU's powershell console, entering 'ldp $hostname' launches a new tab with the ssh session to the host.

This is the only issue preventing me from dropping ConEMU in favor of Windows Terminal.

Originally created by @cadayton on GitHub (Sep 27, 2020). I have hundreds of potential ssh sessions and I don't want to create 100s of custom profiles for each instance. It would helpful if parameterized custom profiles was supported. Also, looking forward to when new-tab can actually open a new tab rather than a new window. Today, I do the following with ConEMU. Define a PowerShell alias 'ldp' (load putty) that does the following. ```putty.exe -new_console -load $hostname``` In a ConEMU's powershell console, entering 'ldp $hostname' launches a new tab with the ssh session to the host. This is the only issue preventing me from dropping ConEMU in favor of Windows Terminal.
claunia added the Resolution-Duplicate label 2026-01-31 02:30:40 +00:00
claunia commented 2026-01-31 02:30:41 +00:00
Author
Owner
Copy Link

@jack775544 commented on GitHub (Sep 29, 2020):

If you use the ssh command line tool instead of putty you can get something similar. If you create a ssh config file then you can connect by using ssh myServer on the command line. Combine this with the ability to run arbitrary commands in new tabs with the ctrl+shift+p menu by prefixing the command with a > character you can open whatever connection you want just by going ctrl+shift+p and then typing >ssh myServer.

@jack775544 commented on GitHub (Sep 29, 2020): If you use the ssh command line tool instead of putty you can get something similar. If you create a [ssh config file](https://futurestud.io/tutorials/simplify-your-ssh-connections-with-ssh-config-file) then you can connect by using `ssh myServer` on the command line. Combine this with the ability to run arbitrary commands in new tabs with the ctrl+shift+p menu by prefixing the command with a `>` character you can open whatever connection you want just by going `ctrl+shift+p` and then typing `>ssh myServer`.
claunia commented 2026-01-31 02:30:41 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 29, 2020):

Combine this with the ability to run arbitrary commands in new tabs with the ctrl+shift+p menu by prefixing the command with a > character you can open whatever connection you want just by going ctrl+shift+p and then typing >ssh myServer.

Wow I didn't even think about that as a potential use case, but that's a great use of the commandline mode of the command palette. Thanks for sharing!

We've got:

  • Add support for inheriting and overriding another profile's settings #3818
  • Add support for wt.exe to run commands in an existing Terminal Window #4472

If you're okay with it opening a new window, wt ssh $hostname will let you run ssh $hostname in a new WT window, with the default profile.

I bet that #4472 would really be the best way to solve this for you, to be able to just do something like wt -s 0 new-tab ssh $hostname. Does that sound like a good solution to you?

@zadjii-msft commented on GitHub (Sep 29, 2020): > Combine this with the ability to run arbitrary commands in new tabs with the ctrl+shift+p menu by prefixing the command with a `>` character you can open whatever connection you want just by going `ctrl+shift+p` and then typing `>ssh myServer`. Wow I didn't even think about that as a potential use case, but that's a great use of the commandline mode of the command palette. Thanks for sharing! <hr> We've got: * Add support for inheriting and overriding another profile's settings #3818 * Add support for wt.exe to run commands in an existing Terminal Window #4472 If you're okay with it opening a new window, `wt ssh $hostname` will let you run `ssh $hostname` in a new WT window, with the default profile. I bet that #4472 would really be the best way to solve this for you, to be able to just do something like `wt -s 0 new-tab ssh $hostname`. Does that sound like a good solution to you?
claunia commented 2026-01-31 02:30:42 +00:00
Author
Owner
Copy Link

@cadayton commented on GitHub (Sep 30, 2020):

I tried the recommendation of ctrl-shift-p and enter '>ssh '. The ssh config was setup up correctly but the console wasn't able to present the password prompt. When I used the full host domain name all worked as expected. Note the new tab value was just duplicated from the original tab. It would be nice if the new tab could have the hostname.

The #4472 option sounds like potential solution. I see making using of the ssh config would be nice too, but not sure why my config is being ignored for some reason.

Here is a work around, I did but the tab value is always a static 'ssh' when using this work around. In the settings, I defined a profile containing:

"command" : "powershell.exe -NoExit psSSH.ps1"

The PowerShell script simply prompts for the needed info to launch a ssh session.

@cadayton commented on GitHub (Sep 30, 2020): I tried the recommendation of ctrl-shift-p and enter '>ssh <hostname>'. The ssh config was setup up correctly but the console wasn't able to present the password prompt. When I used the full host domain name all worked as expected. Note the new tab value was just duplicated from the original tab. It would be nice if the new tab could have the hostname. The #4472 option sounds like potential solution. I see making using of the ssh config would be nice too, but not sure why my config is being ignored for some reason. Here is a work around, I did but the tab value is always a static 'ssh' when using this work around. In the settings, I defined a profile containing: ```"command" : "powershell.exe -NoExit psSSH.ps1"``` The PowerShell script simply prompts for the needed info to launch a ssh session.
claunia commented 2026-01-31 02:30:42 +00:00
Author
Owner
Copy Link

@cadayton commented on GitHub (Sep 30, 2020):

I locked down the .ssh directory so only my account can access it now. The >ssh method has terminal emulation issues when not using the full host domain name and the target host is RHEL. Can ssh to a Cisco switch using PKI and just the hostname and it works perfectly. I'm sort of favoring my work around because I have the option of customizing the profile attributes. I think that I'll trick up the powershell script to use the ssh config file though.

@cadayton commented on GitHub (Sep 30, 2020): I locked down the .ssh directory so only my account can access it now. The >ssh <hostname> method has terminal emulation issues when not using the full host domain name and the target host is RHEL. Can ssh to a Cisco switch using PKI and just the hostname and it works perfectly. I'm sort of favoring my work around because I have the option of customizing the profile attributes. I think that I'll trick up the powershell script to use the ssh config file though.
claunia commented 2026-01-31 02:30:42 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 1, 2020):

Alright, so I'm gonna close this in favor of #4472. Thanks for following up!

/dup #4472

@zadjii-msft commented on GitHub (Oct 1, 2020): Alright, so I'm gonna close this in favor of #4472. Thanks for following up! /dup #4472
claunia commented 2026-01-31 02:30:42 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 1, 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 commented on GitHub (Oct 1, 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!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#10801
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?