Improve handling of unexpected output in tmux integration [was: tmux integration does not properly handle write/wall/mesg commands]

In most *nixes it is possible to write a message to one ore more users using the write/wall/mesg commands. When connecting to a server using ssh -t server "tmux -CC", such a message is not being properly displayed. Instead, it is shown in the "Command Menu" tab after the session has been detached. The expected behaviour is that the text appears immediately, preferably in the currently active tmux tab.

iTerm2 version: Build 2.9.20160313 OS version: 10.11.4

Required information for bugs. I probably can't help you unless you include this:

• iTerm2 version
• OS version
• Attach ~/Library/Preferences/com.googlecode.iterm2.plist here
• Attach a debug log (com.googlecode.iterm2.plistdebuglog.txt

The problem with wall and other programs that write to your tty is that their text is indistinguishable from a response from tmux, which has structure and meaning. Basically anything can happen from corrupted output to making iTerm2 do crazy things if this is used while you're in tmux integration. If you think someone might wall you, run mesg n before tmux. I'm not sure it's worth trying to do something special if someone writes to your tty between tmux responses, since the most common cause of unexpected output is your ssh session dying.

This does raise the question of how best to handle unexpected output. Currently we silently ignore it by default and there's an advanced pref to terminate the connection.

A better option might be to inform the user that unexpected output was received, to display it, and to offer to terminate the connection.

Milestone changed to Feature Complete 3.1

Title changed from tmux integration does not properly handle write/wall/mesg commands to Improve handling of unexpected output in tmux integration [was: tmux integration does not properly handle write/wall/mesg commands]

Milestone changed to Feature Complete 3.2