You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've seen this most commonly while holding down an arrow key to quickly bring the level of a control up/down - basically it looks like some control codes (colors or whatever) get printed onto the screen rather than interpreted "properly", and it can end up remaining on the screen regardless of what you do. For example:
Generally you can clean it up by using F1-F5 to change the rendered controls. I may end up looking into this myself, though I've added a ^L hotkey which completely redraws the screen in my big ol' pull request here: #15 ... I may just make do with that.
The text was updated successfully, but these errors were encountered:
Howdy! I just use plain ol' xterm. I'm actually out of the country for a few weeks and don't have a proper desktop at the moment - I'll run some more tests with this when I get back, though. The screenshot I'd posted above was obviously after my various patches, so it's possible this was something introduced by me. I'd thought that I'd seen it on the vanilla version, but I can't be sure at the moment. I'll let you know eventually!
I've seen this most commonly while holding down an arrow key to quickly bring the level of a control up/down - basically it looks like some control codes (colors or whatever) get printed onto the screen rather than interpreted "properly", and it can end up remaining on the screen regardless of what you do. For example:
Generally you can clean it up by using F1-F5 to change the rendered controls. I may end up looking into this myself, though I've added a ^L hotkey which completely redraws the screen in my big ol' pull request here: #15 ... I may just make do with that.
The text was updated successfully, but these errors were encountered: