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
w # should clear the screen, like in a regular terminal.
Currently it doesn't.
It looks like either even complex commands like
w 1, 2, 3, #, 4, 5, 6
need to be parsed, or, alternatively, the Web Terminal should support at least some of the ANSI escape sequences which come in the server's response. Still, this particular issue may have nothing to do with ANSI escape sequences: if you execute
w #
should clear the screen, like in a regular terminal.Currently it doesn't.
It looks like either even complex commands like
need to be parsed, or, alternatively, the Web Terminal should support at least some of the ANSI escape sequences which come in the server's response. Still, this particular issue may have nothing to do with ANSI escape sequences: if you execute
-- you'll see
123
and456
separated with0x0A
(\n
,^J
) in the server response, while inresponse the same tokens are separated with
0x0D0C
(\r\f
,^M^L
).The text was updated successfully, but these errors were encountered: