Rebanedid you know that SSH has a little-known secret menu?
i wrote a post about this on cohost a while back, but since that site shut down i'm posting it here too
Klaus FrankYes, but did you know that it is basically inaccessible on Keyboard layouts like e.g. de-DE?
Oh and if I recall correctly the keyboard combination is also different on macOS too...
Zimmie@agowa338 @rebane2001 MacOS and Windows both have plain OpenSSH, and the listed escape sequences work on both.
Henrik Pauli@bob_zim @agowa338 @rebane2001 *if* your keyboard layout has a functioning tilde key (a deadkey might output something else and it's nontrivial to make it output just the character itself (and it depends on the OS how it deals with it))
@phl Huh. I’m not sure I’ve seen a non-exotic (e.g, not for a Corne) layout which entirely lacks tilde as a discrete character. On my German keyboards, it’s on the AltGr layer of the +/* key. Same on Spanish QWERTY keyboards I’ve seen.
Not doubting that such a keyboard exists, I just thought I had seen most of the mass-produced layouts.
But the keyboard sequence becomes different and just trying to press it is annoying to impossible. Esp. if you then also try to do it over e.g an additional IPMI or VMware console in between as well.
It's just one of these things that feel like nobody expected anything but en-US being used as it just sucks. Almost always it is easier to first change your keyboard layout to en-US, press the keyboard shortcut, and switch it back...
@agowa338 @phl It doesn’t become a different sequence, though? Immediately after a new line, send a tilde character to signify the next character is a control character, then send the control character (e.g, ? to get the help and command line). Sure, you may press different keys to cause your keyboard to emit the tilde, but that doesn’t make it a different sequence. For example, nobody specifies Shift-/ in these sequences, they specify ?, and it’s up to you to get your keyboard to emit that character.
Yes, software trying to read scan codes directly and interpret them as US keyboards sucks, but that’s hardly the fault of applications like OpenSSH which do no such thing.
@bob_zim @agowa338 I think Klaus might have meant that depending on the layout the actual keys you have to press changes significantly (often not merely by location too)
I have absolutely no clue what I had to press on Hungarian keyboards for ^] in telnet, come to think of it XD I guess it wasn't what I think it was with my now mostly US-layout mind...
@phl @agowa338 Sure, but it’s the operator’s responsibility to know where characters are on the keyboard which they have. I’m currently switching to Colemak-DH on a split ergonomic keyboard, which has a totally custom layout for the non-alphanum keys (e.g, I have [ on the rightmost column of the left keyboard and ] on the leftmost column of the right). It wouldn’t be OpenSSH’s problem (or my OS’s or anybody but mine) if I didn’t give myself a way to type a tilde or if I forgot where it was.
Look, I'm not disagreeing with "the operator should know". However there at least should be some - easily discoverable, or even linked within "man ssh" - kind of documentation for where that combination gets mapped to on STANDARD keyboard layouts. Especially when it changes the entire sequence, not just location...
All I'm complaining about is the lack of documentation and how annoying it was especially when I first learned about that shortcut.