jerch
jerch
Coming from https://github.com/xtermjs/xterm.js/pull/4605 (also see comments there): The consumer of selection change events does too much re-rendering the full viewport. Furthermore the event gets more often sent than needed, this...
On Chrome/Linux I see the following for zoom level 67% in the demo:  (taken with the new DOM renderer, but happens with all - webgl/canvas draw their canvas half...
Early WIP/PoC...
Only playground branch atm... Can be tested with: - call `yarn start` in xterm.js base folder to run demo - insert this into terminal: ``` echo -e 'AAA\x1b[5CBBB\x1bPq#0;2;0;0;0#1;2;100;100;0#2;2;0;100;0#1~~@@vv@@~~@@~~~~@@vv@@~~@@~~~~@@vv@@~~@@~~$#2??}}GG}}??}}????}}GG}}??}}????}}GG}}??}}??\x1b\\\x1b[5CCCC' ``` -...
This is mainly to lift the inwasm build burden from this repo...
Following MDN Firefox recently added better offscreen canvas support in v105, which might give us the chance to optimize canvas/bitmap construction a lot by offloading heavy things to a worker:...
See https://github.com/xtermjs/xterm.js/pull/2503#issuecomment-851036700 for reference...
`echo -e '\x1bPq$-$-$-$-\x1b\\'` should move the text cursor downwards, even if no pixels were modified (given sixel scrolling is on). @hackerb9 If you find some time, can you confirm, that...
In older terminals the graphics output would get printed above any previous content. With backgroundSelect=1 SIXEL has a mode to take advantage of that, where old pixels get not touched,...