Scrollback "sticks" with very long lines. about blightmud

[lisdude]

I tested this with Kitty and the macOS Terminal and it happened in both cases.

I've set up a test server at lisdude.com port 1180. Right now there are two commands:
longline: A single 31,527 character string of real-world output.
random: A random string with no spaces, configurable between 1 and 50,000 characters.

If you can think of more tests we need, I'm happy to add them. Right now, when you run the longline command, you can see that it cuts off the login help text and part of the long line itself. (For reference, the line begins with ";properties(#0)")

[LiquidityC]

The “history” buffer for scroll back is only 1024 lines long so you might be seeing an effect of that here.

Regarding the sticky line this could the client or it could be your terminal not keeping up.

Could you explain how you confirm/test this?

We might need to build a super simple telnet server to be able to test these kind of things.

[LiquidityC]

That is awesome! By the looks of it it seems the history is messed up here and the last lines in the history consist of an "unwrapped" line. At least I have something to work with here. I'll look into it some more.

[LiquidityC]

Just a comment to remind me for later. This might be the prompt acting up. On Servers that don’t send IAC GA we have to guess what’s a prompt when the data stops coming. A simple check here should be that what we think is a prompt is shorter than an arbitrary width. Eg. if it’s longer then 100 chars with no new lines it’s probably not a prompt.