As discussed in sjl/vitality.vim#10, Vitality is inert unless $ITERM_PROFILE is set, meaning that once you ssh to another system it doesn't do much of anything.
I suspect a huge chunk, if not the majority, of tmux sessions are on remote systems. I never use tmux locally, I use it remotely to preserve sessions in case I am cut off from the Internet, or to save sessions on a remote system that are still there after I sleep/wake my laptop.
(Yes, I am aware there are methods to connect a local tmux client to a remote tmux server, but I don't use them and I would guess a whole lot of tmux users do not use them.)
This pull request adds an option to tell Vitality to always assume iTerm is in use. It defaults to off, of course. I am always using iTerm anyway, and the same is probably true of most iTerm users.
FWIW, I tested this in Terminal.app and while Vitality naturally didn't work, it didn't do anything weird (the escape codes were simply ignored as far as I can tell).
As discussed in sjl/vitality.vim#10, Vitality is inert unless $ITERM_PROFILE is set, meaning that once you ssh to another system it doesn't do much of anything.
I suspect a huge chunk, if not the majority, of tmux sessions are on remote systems. I never use tmux locally, I use it remotely to preserve sessions in case I am cut off from the Internet, or to save sessions on a remote system that are still there after I sleep/wake my laptop.
(Yes, I am aware there are methods to connect a local tmux client to a remote tmux server, but I don't use them and I would guess a whole lot of tmux users do not use them.)
This pull request adds an option to tell Vitality to always assume iTerm is in use. It defaults to off, of course. I am always using iTerm anyway, and the same is probably true of most iTerm users.
FWIW, I tested this in Terminal.app and while Vitality naturally didn't work, it didn't do anything weird (the escape codes were simply ignored as far as I can tell).