Issue 286 in shellinabox: ShellInABox Can not clear the contents of the vim buffer

[shell...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 286 by Vrakshe2...@gmail.com: ShellInABox Can not clear the
contents of the vim buffer
https://code.google.com/p/shellinabox/issues/detail?id=286

What steps will reproduce the problem?
1.vim .profile
2.type esc (q!)
3.the content of buffer never clear it is showing on screen


What is the expected output? What do you see instead?
Can not show the vim buffer content if esc quit selected (q!).

What version of the product are you using? On what operating system?
I have using shell-inbox-2.14

Please provide any additional information below.
I have attached images below for more details

Attachments:
vim1.png 27.1 KB
vim2.png 46.0 KB
vim3.png 48.2 KB

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[shell...@googlecode.com]

Comment #1 on issue 286 by neeeesha...@gmail.com: ShellInABox Can not clear

the contents of the vim buffer
https://code.google.com/p/shellinabox/issues/detail?id=286

I am facing a similar issue. It seems that the data received from the
remote terminal after exiting vim is not handled by SIB.

[shell...@googlecode.com]

Comment #2 on issue 286 by luka.kra...@gmail.com: ShellInABox Can not clear

the contents of the vim buffer
https://code.google.com/p/shellinabox/issues/detail?id=286

This works fine for me... Is this easily reproducible or is it happening
just sometimes?

You can try again with this updated fork:
https://github.com/shellinabox/shellinabox

[shell...@googlecode.com]

Comment #3 on issue 286 by Vrakshe2...@gmail.com: ShellInABox Can not clear

the contents of the vim buffer
https://code.google.com/p/shellinabox/issues/detail?id=286

@luka
This does not seem to be an issue with SIB. I have modified SIB
client to only
support VT100 and the remote console seems to be xterm. May be this does
not go well.