-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
True Color not working on Bash on Windows #1733
Comments
This might be a noob question, but do you have a |
@eoinmurphy You can configure the shell you want. Just set @PowerSnail Having 24-bit color could be hard to achieve. Some other term app have some tricks: http://conemu.github.io/en/BashOnWindows.html#wslbridge We need to test |
It does look like xterm.js is working on this (for whenever that transfer is done...) xtermjs/xterm.js#484 |
also, related: #364 |
I know I'm necroing this a bit but is there any fix yet? I really want to use fish with the bobthefish theme and it is unusably bad in hyper when using Windows Subsystem for Linux. |
Would really like to see true color support. Been using this on WSL since it came out, and on my other platforms (Linux and Mac) so all my configs are set for it. I'd really like to switch to Hyper but true color is too nice to give up :) |
And powerline is failing as well and probably because of this (on Windows (!)) :/ See #2470. |
Having the same issue, though I notice that both Hyper and ConEmu, when using Git Bash, have to run it via When I run the same color test script linked by the OP, the true color support works in This makes me wonder if it's more a CMD issue than an issue with Hyper itself... @blark is this an issue for you when using Hyper on Linux or Mac? |
Well, yes -- of course it's an issue with Windows' conhost. But to be clear, that's the underlying console subsytem that all console apps run in. In other words, it's the core difficulty of implementing something like hyper on Windows, and it's not just a problem with a few particular apps or ways of running them. Bottom line: although the console subsystem has seen major improvements in the Windows 10 era (to support ANSI escape sequences, among other things), it's still not based on input/output pipelines the way PTY works on posix subsystems. That's why things like mintty (and wslbridge, which just wraps mintty) make a difference -- when you run apps through them, if the app supports it, then it behaves as though it were running "remotely" (e.g. over SSH) via a pipe (the Linux way, if you will). However, that's not the native way to write or run console apps in Windows, and most interactive Windows console apps --like Python, when used as a REPL-- don't work when run in mintty or other similar emulators. |
So any workground? |
should work in CI builds of canary and the next release |
I am on the latest Hyper.app version
I have searched the issues of this repo and believe that this is not a duplicate
OS version and name: Windows 10
Hyper.app version: 1.3.1
Link of a Gist with the contents of your .hyper.js: Default
Relevant information from devtools (CMD+ALT+I on Mac OS, CTRL+SHIFT+I elsewhere): None
The issue is reproducible in vanilla Hyper.app: Yes
Issue
Bash on Windows supports 24bit true colour with Truecolour escape codes. Running test script that I found here, the following are results from
bash
, and run the script)The text was updated successfully, but these errors were encountered: