I don't think it's very useful for local dev, but it is a lifesaver for SSH work on spotty connections (or any other case where you might want to leave a worksp

I don't think it's very useful for local dev, but it is a lifesaver for SSH work on spotty connections (or any other case where you might want to leave a workspace intact despite losing connection). But if you're already using iTerm, you should just use its built in tmux integration, which lets you keep using iTerm splits and windows while iTerm handles the tmux stuff. You can do this by launching tmux with the -CC option: tmux -CC attach || tmux -CC This is one of my favorite things about iTerm! Combine that with custom profiles for each server and automatic profile switching (and a few other gems), and working remotely is scarcely harder than working locally! The vim stuff is not too hard to get around IIRC. I don't remember the details, but you can have a look at my .vimrc [0] if you want an example that works on remote servers through tmux with iterm. [0] https://github.com/stefco/dotfiles/blob/master/linkfiles/.vimrc https://github.com/stefco/dotfiles/blob/master/linkfiles/.vi...