-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
[Bug Report] incorrect color scheme after getting out of GNU/screen #779
Comments
Update: Downgrading Xterm.js to 3.12.2 fixed this issue. |
Oh nevermind, I saw beta2 in the xterm report. Thanks 😃 |
I'll keep this open - otherwise I'll forget to recheck this when 3.13 is released |
@Eugeny thanks for trying out the beta build, the reports are extremely helpful 🙂 |
@Tyriar you're welcome, can't wait for the webgl renderer to get released! :) I'm going to roll back to 3.12 in the next release though, the Unicode char coloring bug is too much for the users. |
@Eugeny understandable. Yeah I'm having trouble finding time to finish the webgl renderer off, the problem is it has quite a lot of pre-requisites due to the decision not to include it in core (primarily xtermjs/xterm.js#2005, xtermjs/xterm.js#1128). It also just broke because of the UTF32 changes and will need some a little updating to support true color (:tada:). |
@Tyriar |
Any idea how this can be repro'ed with xterm.js demo? Note that for me the prompt correctly changes colors for screen, also reliable for detaching/reattaching (from some greenish thing to blue/red prompt). |
Has been fixed in xterm since. |
Shell: bash
local Platform: macOS 10.14.4 (Mojave)
Steps to reproduce:
screen -S screenName
exit
Same Applies to Ubuntu 18.04.2 LTS with Secure Shell Connection.
The text was updated successfully, but these errors were encountered: