4 ms·
The SSH straight into tmux solution uses RemoteCommand and will break things like scp and rsync [1] I have this in fish config: function tsh ssh -o Requ
by cyounkins 4y ago
The SSH straight into tmux solution uses RemoteCommand and will break things like scp and rsync [1]
I have this in fish config:
function tsh
ssh -o RequestTTY=yes $argv tmux -u -CC new -A -s tmux-main
end
and use `tsh host`
[1] https://unix.stackexchange.com/questions/628607/how-to-bypass-remotecommand-option-in-ssh-config https://unix.stackexchange.com/questions/628607/how-to-bypas...
- CamJN 4y agoWell, it used to break scp, but then I fixed scp: https://github.com/openssh/openssh-portable/commit/77e05394af21d3f5faa0c09ed3855e4505a5cf9f https://github.com/openssh/openssh-portable/commit/77e05394a...
- gerdesj 4y agoTwo lines of code. That was clearly one of those paper cut type of fixes that makes the world a tiny bit nicer.
- dizhn 4y agoI have a similar setup but the tmux invokation is handled on the remote shell. Needless to say it does not break scp. (I will admit that a single config file for all hosts is more convenient though) I am actually switching to having wezterm handling the mux functionality. It's nice to have this stuff running on the local client which allows all familiar keyboard shortcuts to work without conflict. Automatic Pane/Tab support is really nice. Mosh like functionality comes for free as well.
- phaer 4y agoThanks, I personally grew accustomed to just writing "ssh $host 'tmux a || tmux'