A comment about testing, since we have the story now, maybe we can just output more than a screen's worth of text, since with the bug it would render differently than without it, so it should catch this issue.

Or we output some ANSI sequence that writes text to the bottom of the screen. If it displays, we know it is fixed, if not then there is a bug. Or output the terminal size or something.

@BrunoQuaresma for testing, maybe you can write an escape sequence to the terminal that will write something at the bottom? Edit: Actually, this is probably what Asher was suggesting 😄.

For example, the following escape sequence would write to the bottom left and right corners of the terminal: \33[1000BLEFT\33[1000C\33[4DRIGHT

Then you can test if the output is visible?

@mafredri @code-asher good suggestion, I didn't know there was a way to do that. I was just copying and pasting the websocket messages from the terminal.

@mafredri how do you know how to do that? I would add it to my LinkedIn like "Languages: English, ANSI"

@code-asher @mafredri just confirming your suggestion worked! 🙏

@mafredri how do you know how to do that? I would add it to my LinkedIn like "Languages: English, ANSI"

Haha, I will consider it 😉. TBH it was trial and error, I remembered that it was ~ ESC[#X, then I just tried the letters ABCD and saw what happened (I could've just looked it up lol.) Essentially we're moving 1000 blocks in each direction which means we'll hit a wall and stay at the edge, when we do the right one we also go 1000 blocks and then backtrack a few so we have space to output the text. 😄

This looks like a pretty solid intro if you're interested: https://gist.github.com/fnky/458719343aabd01cfb17a3a4f7296797#cursor-controls

Merge activity

• Mar 8, 5:38 AM EST: @BrunoQuaresma merged this pull request with Graphite.