05:18 <dnkl> rockorager: think of foot's scrollback history as a "circular array" of row pointers. The screen (the bottom of the history) is just an index into this array. Scrolling is done by moving the index pointer.

05:19 <dnkl> with left/right margins, that won't work

05:20 <dnkl> given foot's current implementation, the easiest way is probably to memcpy the margin regions to "repair" them after scrolling.

05:26 <dnkl> that said, it's most likely still faster than having the application redraw the contents

09:26 <rockorager> Ah, that makes sense

09:28 <rockorager> Does the alt screen have that same behavior?

09:30 <rockorager> For example, neovim scrolls by deleting the top row and drawing the bottom row...which I wouldn't expect to benefit from that behavior but is still way better than redrawing every line

09:35 <rockorager> Hmm I hadn't thought about the margins in the primary screen - it's a huge pain there the more I think about it

10:14 <dnkl> rockorager: the alt screen is handled the same way, yes.