Hyper: Clear not working on ssh session

[andreacivita]

Hi!
Using hyper i got this error. While i'm connected by SSH to a server (remote or local), i can't use clear command. If i try, i have to exit from ssh session, clear again and re-login.

[albinekb]

• What error?
• What platform
• Version of hyper
• Any plugins?

Steps to reproduce?

Please fill in the issue template

[andreacivita]

• Error: typing "clean" in ssh session make crash of view
• Platform: windows 10
• Version: latest
• No plugin

I attach a screen of error

As you can see, executing clear command does not clear hyper, but create this horrible crash.

[gaganjyot]

Facing same issue in running bash in hyper on windows
What error? unable to clear the screen
What platform -> Windows 10
Version of hyper -> probably 1.3.3 ( downloaded from hyper.is today ).
Steps to reproduce -> Type sommethign, enter some commands. type clear and enter. Or even ctrl + l

[AngelVkz]

The problem still

[chabou]

@andreacivita @gaganjyot
What is the shell of your remote host?

@AngelVkz
Please give us more details: your OS, reproductible without any plugin, screenshot etc...

[andreacivita]

@chabou bash

[ARGibson]

I am also having this issue

• Error: Screen is not cleared when using SSH (either when using tools like nano/vim/screen or when using 'clear' directly)
• Platform: Windows 10 Enterprise
• Version: Latest (1.4.8)
• Plugins: ['hyperterm-paste','hyperline','hyperterm-alternatescroll','hyper-tab-icons','hyper-pane','hyperterm-material','hyperterm-transparent-bg']

The problem occurs without plugins so I have already ruled any of the ones listed out, appears to be an issue with Hyper itself.

To demonstrate, if I have a clear (ha!) screen inside an ssh session:

And then I open a file in nano:

[ARGibson]

After a bit of digging around I came across a similar issue being reported in Git For Windows (
https://github.com/zeit/hyper/issues/1559) which referenced Hyper and adding the TERM environment variable to hyper.js under the env section with a value of either 'cygwin' or 'msys' appears to solve the issue, it certainly has for me.