4 ms·
Windows, AFAIK has a completely different terminal implementation, so I doubt you will ever get the same terminal working on unix-like and windows (modulo the W
by aumerle 10y ago
Windows, AFAIK has a completely different terminal implementation, so I doubt you will ever get the same terminal working on unix-like and windows (modulo the WSL) But as for OS X kitty should be easy to port since it uses only cross platform libraries.
- kalleboo 10y agoHow about with the new Linux-in-Windows stuff? Could you make a terminal emulator that works with just that and ignores cmd/powershell?
- aumerle 10y agoYes, the hard part is replacing cmd.exe (i.e. making a terminal that works with windows programs). Making a terminal that works only with linux programs should be fairly simple, especially with WSL (windows linux subsystem)
- wattengard 10y agoActually cmd.exe isn't the problem. conhost.exe is. Whatever you run on windows CLI, be it CMD, Powershell or BASH, it runs on conhost.exe. Even ConEmu and Console2 are just wrappers around it. The console host is getting better though. The latest W10 release supports arbitrary resizing of the screen atleast :) In the next update we even get 24-bit color. https://blogs.msdn.microsoft.com/commandline/2016/09/22/24-bit-color-in-the-windows-console/ https://blogs.msdn.microsoft.com/commandline/2016/09/22/24-b...