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

Clearer tab title for ssh-configurations immediately running a command like tmux, currently it is just OpenSSH SSH client without hostname #21524

New Issue
Open
opened 2026-01-31 07:47:06 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 07:47:06 +00:00
Owner
Copy Link

Originally created by @fjellvannet on GitHub (Apr 15, 2024).

Description of the new feature/enhancement

It is possible to specify ssh-configurations, so instead of putting e.g. wsl.exe -d ubuntu, one can write ssh user@hostname into the command line field of the configuration to immediately ssh onto a host when a new tab is opened. When the configuration is like that, the tab title looks like this including the hostname (all good):

bilde

However, when I change the configuration to ssh user@hostname -t tmux a to immediately attach to a tmux session, I see the following:

bilde

This is not very handy, as I can't see which host I am connected to, only that it is through ssh. The behaviour is actually exactly the same if I open a powershell tab, and then run ssh user@hostname -t tmux a, also here the title now is just OpenSSH SSH client. If I only run ssh user@hostname in powershell, I see the hostname in the windowtitle as indicated in the first image.

Proposed technical implementation details (optional)

  1. A simple solution to this would be the ability to manually override the tab title for a configuration. Just always show some fixed text.

  2. The nicer solution would be to actually fix the behaviour of how the hostname is displayed when the ssh-command is run with the -t option in General, so that it also works when I manually run the command in powershell.

But as option 2 most likely is more complicated / probably requires changes in the openssh client or the powershell configuration, solution 1 would be sufficient for now.

Originally created by @fjellvannet on GitHub (Apr 15, 2024). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 It is possible to specify ssh-configurations, so instead of putting e.g. wsl.exe -d ubuntu, one can write ssh user@hostname into the command line field of the configuration to immediately ssh onto a host when a new tab is opened. When the configuration is like that, the tab title looks like this including the hostname (all good): ![bilde](https://github.com/microsoft/terminal/assets/22413504/2b8faef3-7477-4025-922c-584655468c75) However, when I change the configuration to ssh user@hostname -t tmux a to immediately attach to a tmux session, I see the following: ![bilde](https://github.com/microsoft/terminal/assets/22413504/573e84c3-ae2a-4945-92fd-320ce16d5c03) This is not very handy, as I can't see which host I am connected to, only that it is through ssh. The behaviour is actually exactly the same if I open a powershell tab, and then run ssh user@hostname -t tmux a, also here the title now is just OpenSSH SSH client. If I only run ssh user@hostname in powershell, I see the hostname in the windowtitle as indicated in the first image. <!-- 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. --> 1. A simple solution to this would be the ability to manually override the tab title for a configuration. Just always show some fixed text. 2. The nicer solution would be to actually fix the behaviour of how the hostname is displayed when the ssh-command is run with the -t option in General, so that it also works when I manually run the command in powershell. But as option 2 most likely is more complicated / probably requires changes in the openssh client or the powershell configuration, solution 1 would be sufficient for now.
claunia added the Issue-FeatureNeeds-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-31 07:47:06 +00:00
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 Issue-Feature Needs-Attention Needs-Tag-Fix Needs-Triage
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#21524
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?