Problems using cmder as an SSH client

[givankin]

Here's what I see when using nano on an ubuntu VM (logged in via SSH using plink - putty command-line client).

Up arrow also doesn't work.

I understand this maybe not an issue of the cmder itself, but I'd be grateful if someone at least points me where to dig. Having to switch back to standard windows terminal sucks.

[givankin]

For comparison, here's how nano looks if opened via standard putty terminal:

[MartiUK]

Try changing /~https://github.com/bliker/cmder/blob/master/vendor/init.bat#L23
from cygwin to xterm.

[givankin]

@MartiUK, didn't help

[MartiUK]

What happens when you use plink through the standard cmd.exe?

[givankin]

It's even worse:

[MartiUK]

It's because putty reads UTF-8 just fine and plink (by itself) does not.

Also, is there a reason why you aren't using the built in ssh.exe?

Try using just ssh in cmder.

[givankin]

@MartiUK built into what, sorry? When I try to just do "ssh" from cmder, I get standard

'ssh' is not recognized as an internal or external command,
operable program or batch file.

[looterz]

Install the full version of cmder that comes with msysgit, or install msysgit ontop of your existing cmder installation, it will add lots of new commands including ssh.

msysgit: /~https://github.com/msysgit/msysgit

[tclancy]

@abbakym I had the same problem, the "ssh" alias for Plink was ahead of the msysgit ssh provided by Cmder. I modified my system (not user) PATH variable, putting C:\Program Files\cmder\vendor\msysgit\bin; at the start of the string.

[givankin]

@looterz @tclancy thanks folks that solved the issue