Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"w #" doesn't clear the screen buffer #22

Closed
unix-junkie opened this issue Mar 27, 2014 · 1 comment
Closed

"w #" doesn't clear the screen buffer #22

unix-junkie opened this issue Mar 27, 2014 · 1 comment

Comments

@unix-junkie
Copy link

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

echo 'w 1, 2, 3, !, 4, 5, 6 h' | /opt/intersystems/cache/2014.1.0/bin/cache -s /opt/intersystems/cache/2014.1.0/mgr

-- you'll see 123 and 456 separated with 0x0A (\n, ^J) in the server response, while in

echo 'w 1, 2, 3, #, 4, 5, 6 h' | /opt/intersystems/cache/2014.1.0/bin/cache -s /opntersystems/cache/2014.1.0/mgr

response the same tokens are separated with 0x0D0C (\r\f, ^M^L).

@nikitaeverywhere
Copy link
Member

Early support of "w #" added. e47da22
Thank you for your request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants