Wez Furlong 127b2a567b add wezterm ssh user@host some command ... This is mostly useful for folks on Windows, as you can also run `wezterm start ssh user@host some command` to run the `ssh` binary in a local pty and let it manage your ssh session. On Windows the local pty currently breaks mouse reporting (see https://github.com/microsoft/terminal/issues/376) so it is desirable to avoid using a local pty if we're going to talk to a remote system. This commit makes it a bit more convenient to establish an ad-hoc ssh session with a pty on a remote host. This method uses libssh2 under the covers and thus doesn't support gssapi, which is potentially frustrating for kerberized environments, but works ok for the majority of users. There are two issues that I want to resolve in follow up work: * The TERM has to be sent very early in the channel establishment, before we "know" the TERM in the `portable-pty` interface. Will need to figure out how to specify that earlier in an appropriate way. * Similarly, if no command is specified, we should request the use of the shell subsystem but we don't have a way to capture this intend with the cmdbuilder. Will need to solve this too.		2019-08-05 09:05:54 -07:00
..
examples	clippy	2019-06-09 07:33:00 -07:00
src	add wezterm ssh user@host some command	2019-08-05 09:05:54 -07:00
Cargo.toml	pty: add ssh support	2019-08-02 10:55:04 -07:00