Leonard Hecker
Leonard Hecker
This is most likely a leftover of the VT responses from WezTerm. The best way to investigate may be to modify this spot to log the received `text` into a...
I do believe everyone here that this is a real issue, because I've seen this exact behavior in other projects a few times already. The only problem is that I...
Logs would not be useful in figuring this out, unfortunately.
This is trivially reproducible in WezTerm, so it may be specific to the older ConPTY it ships with. I guess? In WSL you can test it with: ```sh sh -c...
As mentioned above, wezterm uses an older version of something called ConPTY (which we maintain). It used to be somewhat buggy and has received numerous bug fixes over the last...
Unless I made a mistake, I actually parse OSC sequences at all times, so this should already work as expected. But you reminded me that I investigated this with wezterm...
> What is the red/brown colour on the right hand side? It's a 72-column ruler. When writing commit messages, you're commonly supposed to stay within that number of columns. This...
> In other editors, the text that overruns the size goes red, rather than having a permanent presence on the screen. The current design is just a result of simplifying...
I merged most of your suggestions into #596. I did credit you as a co-author but forgot to link the PR. I apologize for that. Thank you for the improvements!
That's curious... Since most code is platform-independent, and the TUI code certainly is, it makes this issue highly suspicious. Could this perhaps be some sort of UB? I think it's...