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

SSH profiles without HostName won't be generated #23747

New Issue
Closed
opened 2026-01-31 08:51:19 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 08:51:19 +00:00
Owner
Copy Link

Originally created by @gmsj0001 on GitHub (Oct 23, 2025).

Host 192.168.1.1
  User root

This is a valid config but WT requires a HostName line

Originally created by @gmsj0001 on GitHub (Oct 23, 2025). ``` Host 192.168.1.1 User root ``` This is a valid config but WT requires a HostName line
claunia commented 2026-01-31 08:51:22 +00:00
Author
Owner
Copy Link

@Karsod58 commented on GitHub (Oct 24, 2025):

I suggest adding HostName 192.168.1.1 as it's the simplest fix that maintains compatibility with both SSH and Windows Terminal while keeping your existing workflow intact. Like Host 192.168.1.1
HostName 192.168.1.1
User root

@Karsod58 commented on GitHub (Oct 24, 2025): I suggest adding HostName 192.168.1.1 as it's the simplest fix that maintains compatibility with both SSH and Windows Terminal while keeping your existing workflow intact. Like Host 192.168.1.1 HostName 192.168.1.1 User root
claunia commented 2026-01-31 08:51:22 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 29, 2025):

Thanks for filing! For now, this one is by design. The thing is, we've been trying to figure out the right balance between creating useful profiles and inundating users with useless cruft.

My SSH config has a bunch of lines line this:

Host a b c d
    User foo

I don't think we should create four profiles from that. I don't know if we should create one, either. Which one? It's not a... and it's not d.

We decided that we wanted to make profile for "aliases" (think shorthand for SSHing somewhere), and Host and HostName were the best heuristic we could agree on for figuring out what endpoints people were making aliases for.

@DHowett commented on GitHub (Oct 29, 2025): Thanks for filing! For now, this one is by design. The thing is, we've been trying to figure out the right balance between creating useful profiles and inundating users with useless cruft. My SSH config has a bunch of lines line this: ``` Host a b c d User foo ``` I don't think we should create four profiles from that. I don't know if we should create _one_, either. Which one? It's not `a`... and it's not `d`. We decided that we wanted to make profile for "aliases" (think shorthand for SSHing somewhere), and `Host` and `HostName` were the best heuristic we could agree on for figuring out what endpoints people were making _aliases_ for.
claunia commented 2026-01-31 08:51:22 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 29, 2025):

If we were to revamp how dynamic profiles work so that they don't permanently write profiles into your config file and were instead searchable launchable tasks... we may revisit this. For now, though, no. :)

@DHowett commented on GitHub (Oct 29, 2025): If we were to revamp how dynamic profiles work so that they don't permanently write profiles into your config file and were instead searchable launchable tasks... we may revisit this. For now, though, no. :)
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 Area-Settings Help Wanted Issue-Bug Needs-Tag-Fix Needs-Triage Priority-3 Product-Terminal Resolution-By-Design
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#23747
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?