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
Normally if one gets the terminal in a messed up state, a person can blindly type reset^J to fix the problem. This does not work in Yaft as it does not turn off sixel input when it gets a reset sequence.
For example, if someone accidentally writes a binary file to their screen and it contains the sequence ESCP, then YAFT will appear to lock up. Typing anything, even reset, has no effect.
One solution would be to add the ESC\ sequence to the terminfo reset string. However, it would be better if YAFT simply turned off Sixel input when it got the normal reset string.
By the way, in xterm, the clear screen escape sequence seems to also turn off sixel input. You can try this from the terminal:
echo $'\eP'
# now terminal appears frozen
clear # Or press control-L
# now terminal works again
It would be nice if Yaft worked similarly.
The text was updated successfully, but these errors were encountered:
Normally if one gets the terminal in a messed up state, a person can blindly type
reset^J
to fix the problem. This does not work in Yaft as it does not turn off sixel input when it gets a reset sequence.For example, if someone accidentally writes a binary file to their screen and it contains the sequence
ESC
P
, then YAFT will appear to lock up. Typing anything, evenreset
, has no effect.One solution would be to add the
ESC
\
sequence to the terminfo reset string. However, it would be better if YAFT simply turned off Sixel input when it got the normal reset string.By the way, in
xterm
, the clear screen escape sequence seems to also turn off sixel input. You can try this from the terminal:It would be nice if Yaft worked similarly.
The text was updated successfully, but these errors were encountered: