-
Notifications
You must be signed in to change notification settings - Fork 49
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
Switch to xterm.js #25
Conversation
cc @spadgett still need to figure out why it doesn't seem to be honoring cols correctly |
@stefwalter do you have concerns about the visible scrollbar in general #25 (comment) There a lot of things about the xterm behavior (plus long term support) that seem better at this point, so I think we definitely want to switch to it for openshift but I don't want to break things for cockpit. If necessary we will fork container-terminal and use our own version based on xterm. Let me know. |
I think xterm is the right way forward. Lets not fork. We pull a specific older version of container-terminal, but would update to this soon. |
FYI @petervo |
We'll cut a major version (2.0) when we release this since its a big underlying change |
Seeing weird scrollback behavior with the keyboard in applications like vi and less, partially improved by setting applicationCursor:true remaining issue seems to only happen if you arrow down a couple times and then arrow ALL the way back to the top, then the scrollback buffer isnt getting cleared out. If you arrow back only part way then the scrollback seems to contain the content you would expect. |
Just wanted to note: After we merge this, we should bump the Y number of the package, as this is more than just a micro update. Thanks for the effort here. |
The remaining issue is minor relative to the benefits we gain, its being tracked upstream at xtermjs/xterm.js#802 would propose merging this, @spadgett ? |
+1 -- I don't think that issue should block us from going ahead. This fixes a lot more problems than it introduces |
No description provided.