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

How about make microsoft terminal can be used on mac osx or linux #817

New Issue
Closed
opened 2026-01-30 22:05:20 +00:00 by claunia · 11 comments
claunia commented 2026-01-30 22:05:20 +00:00
Owner
Copy Link

Originally created by @ghost on GitHub (May 8, 2019).

How about make microsoft terminal can be used on mac osx or linux.

I am using both windows and linux .

the new microsoft terminal looks good.

can it be ship to mac osx and linux ?

Originally created by @ghost on GitHub (May 8, 2019). How about make microsoft terminal can be used on mac osx or linux. I am using both windows and linux . the new microsoft terminal looks good. can it be ship to mac osx and linux ?
claunia added the Issue-QuestionResolution-Duplicate labels 2026-01-30 22:05:20 +00:00
claunia commented 2026-01-30 22:05:21 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 8, 2019):

Hi! Thanks for the interest. Since we depend on some parts of the Windows platform, that’s not an option for us. Sorry!

@DHowett-MSFT commented on GitHub (May 8, 2019): Hi! Thanks for the interest. Since we depend on some parts of the Windows platform, that’s not an option for us. Sorry!
claunia commented 2026-01-30 22:05:21 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 8, 2019):

#504 dupe

@DHowett-MSFT commented on GitHub (May 8, 2019): #504 dupe
claunia commented 2026-01-30 22:05:21 +00:00
Author
Owner
Copy Link

@dinfyru commented on GitHub (May 8, 2019):

t_t

@dinfyru commented on GitHub (May 8, 2019): t_t
claunia commented 2026-01-30 22:05:22 +00:00
Author
Owner
Copy Link

@zinking commented on GitHub (Jun 5, 2019):

with windows having 2 kernels now, I'd suggest seriously consider support other platforms. I might moving back to windows because of this.

@zinking commented on GitHub (Jun 5, 2019): with windows having 2 kernels now, I'd suggest seriously consider support other platforms. I might moving back to windows because of this.
claunia commented 2026-01-30 22:05:22 +00:00
Author
Owner
Copy Link

@miguelusque commented on GitHub (Jul 22, 2020):

Hi all,

First of all, thank you for this great product. I ❤️ it.

About the following comment:

Since we depend on some parts of the Windows platform, that’s not an option for us. Sorry!

I understand that you make use of some parts of the Windows platform, but I was wondering if there is no equivalent to that functionality in other Operating Systems, like MacOS or Linux.

Is it so tight the integration with Windows OS which makes so hard to port to other OSs?

Thanks! And congrats again for the great work you are all doing!

Regards,
Miguel

@miguelusque commented on GitHub (Jul 22, 2020): Hi all, First of all, thank you for this great product. I ❤️ it. About the following comment: > Since we depend on some parts of the Windows platform, that’s not an option for us. Sorry! I understand that you make use of some parts of the Windows platform, but I was wondering if there is no equivalent to that functionality in other Operating Systems, like MacOS or Linux. Is it so tight the integration with Windows OS which makes so hard to port to other OSs? Thanks! And congrats again for the great work you are all doing! Regards, Miguel
claunia commented 2026-01-30 22:05:22 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 22, 2020):

@miguelusque See https://github.com/microsoft/terminal/issues/6074#issuecomment-632028446:

From https://github.com/microsoft/terminal/issues/4235#issuecomment-574748858

We're dependent upon C++/WinRT and XAML Islands (UWP XAML) for our UI. We're also using DX/DWrite for the text renderer. Unless those are ported to linux sometime, then I'd say there's very little chance we ever support linux.

s/linux/macOS/

@zadjii-msft commented on GitHub (Jul 22, 2020): @miguelusque See https://github.com/microsoft/terminal/issues/6074#issuecomment-632028446: > From https://github.com/microsoft/terminal/issues/4235#issuecomment-574748858 > > > We're dependent upon C++/WinRT and XAML Islands (UWP XAML) for our UI. We're also using DX/DWrite for the text renderer. Unless those are ported to linux sometime, then I'd say there's very little chance we ever support linux. > > s/linux/macOS/
claunia commented 2026-01-30 22:05:22 +00:00
Author
Owner
Copy Link

@miguelusque commented on GitHub (Jul 31, 2020):

Hi @zadjii-msft ,

I understand the current status, thank you for your swift reply.

Nevertheless, Microsoft has proven to be able to develop software which runs on multiple platforms, i.e.: Microsoft Visual Studio Code, Microsoft Teams, Microsoft Office...

Therefore, I am keen to think that it is not because of technical issues why a MacOS/Linux version is not available yet, but a matter of other priorities and/or project planning.

Once again, congratulations for the great work done.

Regards,
Miguel

@miguelusque commented on GitHub (Jul 31, 2020): Hi @zadjii-msft , I understand the current status, thank you for your swift reply. Nevertheless, Microsoft has proven to be able to develop software which runs on multiple platforms, i.e.: Microsoft Visual Studio Code, Microsoft Teams, Microsoft Office... Therefore, I am keen to think that it is not because of technical issues why a MacOS/Linux version is not available yet, but a matter of other priorities and/or project planning. Once again, congratulations for the great work done. Regards, Miguel
claunia commented 2026-01-30 22:05:22 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 31, 2020):

Visual Studio Code and Teams are Electron applications which are fundamentally web apps, so they're trivial to make cross platform. However, they do come with the burden of the entire Electron runtime, and that's something that we weren't comfortable with on the Terminal team. We wanted to make sure to build a native application so that in the long run, the Terminal would have a smaller memory commit and be far more performant than we could ever get with Electron.

Office on the other hand has been around for decades and has an enormous team of engineers. I'm not sure what tech stack they're using, but I'm sure that once they got the apps running cross-platform, it was easier to maintain that. Plus, with their larger teams, it's probably easier for them to maintain two different UI stacks (one for Windows and one for OSX). They likely have a team of engineers for the Windows version and a separate team for the Mac version. With the 4 of us on the Terminal, I'm not sure it's really feasible for us to try and support an entirely separate UI stack.

If WinUI, DirectX, and WinRT were available on OSX, then it would be trivial for us to port the Terminal to MacOS. Those are all critical components in how the Terminal is built. Replacing any one of them with a cross-platform solution would be an enormous undertaking, if it's possible at all.

So you're probably not wrong. There might be replacements for each of those components. We could use (whatever the UI stack on OSX is), OpenGL, and (something?) to replace them. But it absolutely is not a priority for us when we'd rather work on improving the developer experience here on Windows first and foremost. We'd rather be working on hyperlinks in the Terminal (#574 #204), or adding support for a default Terminal application (#492), or tab tearout (#5000), or application theming (#3327), or Mark Mode(#5804), or Quake Mode (#653), or any of the other 1000 open issues on this repo. Adding support for OSX would mean pushing a bunch of those features back by at least a year.

So that's where I'm coming from.

@zadjii-msft commented on GitHub (Jul 31, 2020): Visual Studio Code and Teams are [Electron](https://www.electronjs.org/) applications which are fundamentally web apps, so they're trivial to make cross platform. However, they do come with the burden of the entire Electron runtime, and that's something that we weren't comfortable with on the Terminal team. We wanted to make sure to build a native application so that _in the long run_, the Terminal would have a smaller memory commit and be far more performant than we could ever get with Electron. Office on the other hand has been around for decades and has an enormous team of engineers. I'm not sure what tech stack they're using, but I'm sure that once they got the apps running cross-platform, it was easier to maintain that. Plus, with their larger teams, it's probably easier for them to maintain two different UI stacks (one for Windows and one for OSX). They likely have a team of engineers for the Windows version and a separate team for the Mac version. With the _4_ of us on the Terminal, I'm not sure it's really feasible for us to try and support an entirely separate UI stack. If WinUI, DirectX, and WinRT were available on OSX, then it would be _trivial_ for us to port the Terminal to MacOS. Those are all critical components in how the Terminal is built. Replacing any one of them with a cross-platform solution would be an enormous undertaking, if it's possible at all. So you're probably not wrong. There might be replacements for each of those components. We could use (whatever the UI stack on OSX is), OpenGL, and (something?) to replace them. But it absolutely is not a priority for us when we'd rather work on improving the developer experience here on Windows first and foremost. We'd rather be working on hyperlinks in the Terminal (#574 #204), or adding support for a default Terminal application (#492), or tab tearout (#5000), or application theming (#3327), or Mark Mode(#5804), or Quake Mode (#653), or any of the other 1000 open issues on this repo. Adding support for OSX would mean pushing a bunch of those features back by at least a year. So that's where I'm coming from.
claunia commented 2026-01-30 22:05:23 +00:00
Author
Owner
Copy Link

@tracker1 commented on GitHub (Aug 21, 2020):

@miguelusque you might want to take a look at hyper It's not quite the same, but offers some similar features and is cross platform. It's what I tend to use in Linux. On mac I use iTerm2 and on Windows I'm using Windows Terminal.

@tracker1 commented on GitHub (Aug 21, 2020): @miguelusque you might want to take a look at [hyper](https://hyper.is/) It's not quite the same, but offers some similar features and is cross platform. It's what I tend to use in Linux. On mac I use iTerm2 and on Windows I'm using Windows Terminal.
claunia commented 2026-01-30 22:05:23 +00:00
Author
Owner
Copy Link

@danielktdoranie commented on GitHub (Sep 8, 2020):

How about make microsoft terminal can be used on mac osx or linux.

I am using both windows and linux .

the new microsoft terminal looks good.

can it be ship to mac osx and linux ?

LOL no thanks ha ha ha

@danielktdoranie commented on GitHub (Sep 8, 2020): > How about make microsoft terminal can be used on mac osx or linux. > > I am using both windows and linux . > > the new microsoft terminal looks good. > > can it be ship to mac osx and linux ? LOL no thanks ha ha ha
claunia commented 2026-01-30 22:05:24 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 8, 2020):

@danielktdoranie was it necessary for you to let everybody subscribed to this repository that you don't particularly care for somebody's rejected feature request? No? Well.

@DHowett commented on GitHub (Sep 8, 2020): @danielktdoranie was it necessary for you to let everybody subscribed to this repository that you don't particularly care for somebody's _rejected feature request_? No? Well.
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-Question 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#817
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?