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

Window Terminal version for Linux, BSD, MasOS - Native Gui or Wine #17754

New Issue
Closed
opened 2026-01-31 05:52:22 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 05:52:22 +00:00
Owner
Copy Link

Originally created by @fischerdouglas on GitHub (Jun 20, 2022).

Description of the new feature/enhancement

Create a Windows Terminal package release chain for use on Linux/BSD/MacOS.
Possibilities:

  • Package that runs directly in the graphical environment of the operating system (Gnome and sons, KDE and sons.)
  • Adjust the package for Windows so that it works as properly as possible in Wine (and similar)

Proposed technical implementation details (optional)

I don't have a technical proposition on how to implement this!
I don't even know how feasible this is technically speaking...

However, taking most MegaThreads as a reference, most of them have some comparison of functionality with terminal tools that are used on Linux, BSD, and MacOS.

I have the impression that if it were possible for this tool to be more accessible to users of Linux, BSD, and MacOS, it would bring these more controversial problems to the table more explicitly. Both for the really technical development discussions, and for the functionality comparison discussions.

This probably doesn't make much sense if we think that the primary focus of Windows Terminal is on the good interoperability of the Command Prompt with the terminal tool through its API. But I think this can bring benefits, including the idea of popularizing the use of Powershell in the Linux environment.

Originally created by @fischerdouglas on GitHub (Jun 20, 2022). # Description of the new feature/enhancement Create a Windows Terminal package release chain for use on Linux/BSD/MacOS. Possibilities: - Package that runs directly in the graphical environment of the operating system (Gnome and sons, KDE and sons.) - Adjust the package for Windows so that it works as properly as possible in Wine (and similar) # Proposed technical implementation details (optional) I don't have a technical proposition on how to implement this! I don't even know how feasible this is technically speaking... However, taking most MegaThreads as a reference, most of them have some comparison of functionality with terminal tools that are used on Linux, BSD, and MacOS. I have the impression that if it were possible for this tool to be more accessible to users of Linux, BSD, and MacOS, it would bring these more controversial problems to the table more explicitly. Both for the really technical development discussions, and for the functionality comparison discussions. This probably doesn't make much sense if we think that the primary focus of Windows Terminal is on the good interoperability of the Command Prompt with the terminal tool through its API. But I think this can bring benefits, including the idea of popularizing the use of Powershell in the Linux environment.
claunia added the Issue-FeatureNeeds-TriageNeeds-Tag-Fix labels 2026-01-31 05:52:22 +00:00
claunia commented 2026-01-31 05:52:25 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 20, 2022):

This one's already in the FAQ:

Unfortunately no, and we have no plans to make the Terminal available on operating systems below version 1903. There are some important operating system features we depend on. Namely:

  • XAML Islands is the technology we use to host our XAML UI in a Win32 process. Without that, we'd be unable to display anything. Since XAML Islands is only complete as of 1903, there's nothing we can do about it.
  • 1903 Also added support for side-by-side WinRT component activation, something deep in the COM stack that lets us find our DLLs when they're right next to our EXE.

The answer is actually basically the same as the above. Windows Terminal requires a good number of Windows-specific technologies. We unfortunately won't be supporting it on Mac or anywhere else any time soon. There are some really good terminals on OS X, including iTerm and Hyper, and an uncountable number of good terminals on Linux.

@zadjii-msft commented on GitHub (Jun 20, 2022): This one's already [in the FAQ](https://github.com/microsoft/terminal/wiki/Frequently-Asked-Questions-(FAQ)#what-about-porting-the-windows-terminal-to-macos-or-linux): > Unfortunately no, and we have no plans to make the Terminal available on operating systems below version 1903. There are some important operating system features we depend on. Namely: > > * XAML Islands is the technology we use to host our XAML UI in a Win32 process. Without that, we'd be unable to display anything. Since XAML Islands is only complete as of 1903, there's nothing we can do about it. > * 1903 Also added support for side-by-side WinRT component activation, something deep in the COM stack that lets us find our DLLs when they're right next to our EXE. > The answer is actually basically the same as the above. Windows Terminal requires a good number of Windows-specific technologies. We unfortunately won't be supporting it on Mac or anywhere else any time soon. There are some really good terminals on OS X, including iTerm and Hyper, and an uncountable number of good terminals on Linux.
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-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#17754
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?