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

Microsoft Terminal sets TERM=xterm-256color instead of TERM=ms-terminal #12892

New Issue
Closed
opened 2026-01-31 03:28:12 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 03:28:12 +00:00
Owner
Copy Link

Originally created by @pagerc on GitHub (Mar 7, 2021).

Microsoft Terminal is not XTerm and does not conform with xterm-256color and therefore should not claim conformance to its terminfo capabilities.

Please update the terminfo database (per #8303) with Thomas Dickey to match more closely to Microsoft Terminal as it is today, and change the default TERM value from xterm-256color to ms-terminal.

A possible workaround is to add configuration options so that users can configure their MSTerm profile and specify the TERM variable that will be set instead of using the default xterm-256color.

Originally created by @pagerc on GitHub (Mar 7, 2021). Microsoft Terminal is *not* `XTerm` and does not conform with `xterm-256color` and therefore should not claim conformance to its terminfo capabilities. Please update the terminfo database (per #8303) with Thomas Dickey to match more closely to Microsoft Terminal as it is today, and change the default TERM value from `xterm-256color` to `ms-terminal`. A possible workaround is to add configuration options so that users can configure their MSTerm profile and specify the TERM variable that will be set instead of using the default `xterm-256color`.
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-31 03:28:12 +00:00
claunia commented 2026-01-31 03:28:13 +00:00
Author
Owner
Copy Link

@pagerc commented on GitHub (Mar 7, 2021):

In a tangentially related issue, setting WSLENV=TERM causes TERM to be undefined in MS Terminal.
In wsltty, a terminal type such as mintty can be set so that it doesn't reuse a broken xterm related hack.

@pagerc commented on GitHub (Mar 7, 2021): In a tangentially related issue, setting `WSLENV=TERM` causes `TERM` to be undefined in MS Terminal. In wsltty, a terminal type such as `mintty` can be set so that it doesn't reuse a broken `xterm` related hack.
claunia commented 2026-01-31 03:28:14 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Mar 7, 2021):

We don’t set TERM, WSL does. Sorry!

@DHowett commented on GitHub (Mar 7, 2021): We don’t set TERM, WSL does. Sorry!
claunia commented 2026-01-31 03:28:14 +00:00
Author
Owner
Copy Link

@pagerc commented on GitHub (Mar 7, 2021):

We don’t set TERM, WSL does. Sorry!

Then that's the bug, that MS Terminal doesn't provide a means of overriding the TERM environment variable at launch time of the chosen shell.

@pagerc commented on GitHub (Mar 7, 2021): > We don’t set TERM, WSL does. Sorry! Then that's the bug, that MS Terminal doesn't provide a means of overriding the TERM environment variable at launch time of the chosen shell.
claunia commented 2026-01-31 03:28:14 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Mar 7, 2021):

Unfortunately, WSL sets that environment variable after it launches. It’s hard to override things that happen after you’ve ceded control :)

@DHowett commented on GitHub (Mar 7, 2021): Unfortunately, WSL sets that environment variable _after_ it launches. It’s hard to override things that happen after you’ve ceded control :)
claunia commented 2026-01-31 03:28:14 +00:00
Author
Owner
Copy Link

@pagerc commented on GitHub (Mar 10, 2021):

Must be a discrepancy in how WSLTTY and MS Terminal launch WSL. I think WSLTTY is using wslbridge2, so that's probably what it's able to have set the environment on the shell before execing it.

@pagerc commented on GitHub (Mar 10, 2021): Must be a discrepancy in how WSLTTY and MS Terminal launch WSL. I think WSLTTY is using wslbridge2, so that's probably what it's able to have set the environment on the shell before execing it.
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 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#12892
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?