That doesn't do much good if you set `EscapeChar` to `none` in `.ssh/config`.

I find it convenient not to have to worry about accidentally entering escape characters. YMMV.

Note that it only works after pressing enter, so the odds are slim. In practice, I don't think I ever hit it by accident.

▲

greyface- 3 hours ago | parent [-]

I have noticed it while running ~/bin/some_command. The ~ doesn't echo until I also type the /. It doesn't cause any misbehavior because there is no binding for ~/ but can be slightly surprising.

	▲	singlow an hour ago \| parent [-]
		I find it odd that you would have commands in ~/bin but not have it be the highest priority in your PATH. I use ~/.local/bin, but would never type it because i wouldn't have bins that overlap shell commands and no other path would have priority.

▲

wolvoleo 3 hours ago | parent | prev [-]

SSH does it pretty well though. Never once have I done it by mistake.

▲

jasomill an hour ago | parent [-]

I'd guess this is because it only works in ssh PTY sessions. So it would have no effect on tunneling or when piping arbitrary data through ssh to a non-interactive remote command (unless you use the -t switch to force PTY allocation even when stdin is not a TTY).

	▲	wolvoleo an hour ago \| parent [-]
		No I don't think so. I mainly and pretty much constantly use SSH for logging in. I'm not one of those 'cattle not pets' guys lol. And when I port forward I usually don't even tunnel it over SSH because all my stuff is on tailscale so it's also encrypted.