Why does some key combinations not work over ssh?
-
OH!!!! Not MeshCentral. We talk about MC so often, it never occurred to me that it would be something else.
-
Well that just changes everything and makes SO much more sense now.
-
@scottalanmiller said in Why does some key combinations not work over ssh?:
OH!!!! Not MeshCentral. We talk about MC so often, it never occurred to me that it would be something else.
That's why I used mc instead of MC
-
@Pete-S said in Why does some key combinations not work over ssh?:
@scottalanmiller said in Why does some key combinations not work over ssh?:
OH!!!! Not MeshCentral. We talk about MC so often, it never occurred to me that it would be something else.
That's why I used mc instead of MC
JAJA, okay. You got me there.
"mc" installed so that I can test...
-
Okay, so the commands work locally for me now
-
@scottalanmiller said in Why does some key combinations not work over ssh?:
Okay, so the commands work locally for me now
OK.
I have two identical debian VMs (clones), with openssh, no xwindows.
When I start mc locally and edit a file (press F4 and pick mcedit) I can use the keyboard and move the cursor word by word by using (ctrl+left/right arrow) inside the editor.
This works fine on both.
If I however open an ssh connection from one to the other server and then start mc and edit the same file, the same keyboard combinations (ctrl+left/right arrow) doesn't work.
-
OK, test 2.
Installed two identical Fedora 30 Servers in VMs (clones).
Using mc locally and edit a file => ctrl+left/right arrow works.
SSH to the other server and start mc and edit same file => ctrl+left/right arrow doesn't work.
So the results are the same as on the debian servers. Are some keyboard "codes" lost over ssh, or is there something else going on?
-
OK, test 3.
This is even more straight forward.
Start mc locally and edit a file => ctrl+left/right arrow works.
SSH to localhost, start mc and edit same file => ctrl+left/right arrow doesn't work.
-
So the issue is that SSH uses the ASCII definitions for what can be passed, and things like Control-Shift aren't defined in the ASCII C0 control set.
https://en.wikipedia.org/w/index.php?title=C0_and_C1_control_codes&oldid=869654887#C0_controls
So they aren't passed because they aren't part of the character set of the protocol. So yes, it's SSH not passing it because it doesn't exist to SSH
-
@scottalanmiller said in Why does some key combinations not work over ssh?:
So the issue is that SSH uses the ASCII definitions for what can be passed, and things like Control-Shift aren't defined in the ASCII C0 control set.
https://en.wikipedia.org/w/index.php?title=C0_and_C1_control_codes&oldid=869654887#C0_controls
So they aren't passed because they aren't part of the character set of the protocol. So yes, it's SSH not passing it because it doesn't exist to SSH
That's too bad.
Do you have any link where it says that ssh uses these definitions? Maybe there is a way around it.
-
@Pete-S said in Why does some key combinations not work over ssh?:
@scottalanmiller said in Why does some key combinations not work over ssh?:
So the issue is that SSH uses the ASCII definitions for what can be passed, and things like Control-Shift aren't defined in the ASCII C0 control set.
https://en.wikipedia.org/w/index.php?title=C0_and_C1_control_codes&oldid=869654887#C0_controls
So they aren't passed because they aren't part of the character set of the protocol. So yes, it's SSH not passing it because it doesn't exist to SSH
That's too bad.
Do you have any link where it says that ssh uses these definitions? Maybe there is a way around it.
Can't find one, not with OpenSSH. Tectia supports it, but is crap in general. If you search on it, everyone talks about the ASCII limits of SSH. You'll find SFTP / SCP have the ASCII / Binary option for connections because of the underlying ASCII protocol in use.
-
@scottalanmiller said in Why does some key combinations not work over ssh?:
@Pete-S said in Why does some key combinations not work over ssh?:
@scottalanmiller said in Why does some key combinations not work over ssh?:
So the issue is that SSH uses the ASCII definitions for what can be passed, and things like Control-Shift aren't defined in the ASCII C0 control set.
https://en.wikipedia.org/w/index.php?title=C0_and_C1_control_codes&oldid=869654887#C0_controls
So they aren't passed because they aren't part of the character set of the protocol. So yes, it's SSH not passing it because it doesn't exist to SSH
That's too bad.
Do you have any link where it says that ssh uses these definitions? Maybe there is a way around it.
Can't find one, not with OpenSSH. Tectia supports it, but is crap in general. If you search on it, everyone talks about the ASCII limits of SSH. You'll find SFTP / SCP have the ASCII / Binary option for connections because of the underlying ASCII protocol in use.
Thanks, I'll dig around and see if I can find something. Otherwise I'll just have accept that it is what it is
