Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
ConEmu\CMDER and WSL | finding a non-broken terminal emulator #1738
Issue was probably mentioned in many variations, But I can't find a proper closure for this subject. That's why this ticket is open.
ConEmu build: 180626 x32/x64
For a while I've been trying to get this bash to work through ssh with connecting to many servers in my company that run centos (currently on 7.5.XXX), a while ago there were a few 6.X).
Actual problem - Ctrl+ K to delete a line in nano - text is broken and not seen on screen.
any chance you know which terminal emulator would work best? (I mean a TERM environment variable)
Steps to reproduce
the nano editor would look the same even though that line was deleted.
the display should refresh and the line should've disappear
Any thoughts anyone? I'm banging my head hard trying to figure that one out, but using that "vt220' really turned things around for the best with all the bash\wsl issues everyone had here.
Thank you all!
So new info -
So any kind of help on that topic, i'd really appreciate, thanks again!
I think I found a solution for that, but I will do further testing in hope I don't destroy files in the background.
Yea, exactly that. My examples above are from bash in windows, That work through conemu/cmder.
Wow! Good job man. I’ll give it a try tomorrow. I’m just wondering how it works with centos or Debian will they understand it when opening nano?…
Sent from my iPhone
On 20 Apr 2019, at 04:22, zaphod77 ***@***.***> wrote: try set TERM=ansi conemu can handle ansi. it's xterm emulation is buggy, most likely because it is passing through to windows 10s, which is incomplete. oddly enough CMDer has it fixed, and properly supports xterm. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
@zaphod77 - well unfortunately, I'm using CMDer but neither xterm nor ansi works well there mate
i use cmder and run win32 ssh directly under that. and pico works just fine.
what editor is failing to work?
I just used default setup for CMDer.
Depending on what it used, as long as there is accurate terminfo or termcap data on the remote system.
Can you give me a test case that fails with non WSL ssh win32 under CMDer that isn't mouse related?