You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Complexity: 4 (ideally someone fairly familiar with terminals and curses apps)
Much of the terminal frontend xterm.js was rewritten for performance this version, here is a summary of what happened:
The parser was rewritten for performance
A catch up mechanism was added which utilizes XOFF/XON signals to tell the pty process to stop while the parser and renderer catch up
Rendering is now done asynchronously in an animation frame callback
Additional frame skipping was added to prevent printing to the viewport when the result would change 20ms later anyway
A circular list is now used to manage the buffer, promoting memory reuse, reducing GCs and automatically handling trimming of the buffer to conform with the scrollback value (amount of lines kept in the buffer)
General rendering performance improvements
Additionally on Windows the library used to simulate pseudoterminals has been upgraded several versions and cleaned up which was a huge change that should fix many bugs such as:
Tested with PowerShell & cmd.exe. I tested it with Bash from the Windows Subsystem started from a PowerShell command prompt. Couldn't get it to work using bash natively.
Testing #13625, #17875
Complexity: 4 (ideally someone fairly familiar with terminals and curses apps)
Much of the terminal frontend xterm.js was rewritten for performance this version, here is a summary of what happened:
Additionally on Windows the library used to simulate pseudoterminals has been upgraded several versions and cleaned up which was a huge change that should fix many bugs such as:
As a result a fairly broad test would be ideal. Here are some areas to focus on:
ls -lR
extensively to test during developmentThe text was updated successfully, but these errors were encountered: