broken pipe message is printed internally and can't be caught by a trigger
Thanks for filing an issue! Please answer the questions below so I can help you.
- iTerm2 version: 3.0.5
- OS version: OS X 10.11.6
- Attach ~/Library/Preferences/com.googlecode.iterm2.plist here (drag-drop from finder into this window)
- Attach a debug log, if possible. Instructions at https://iterm2.com/debuglog
- Are you reporting a performance issue or a hang? Please attach a sample. Instructions at https://gitlab.com/gnachman/iterm2/wikis/HowToSample
- Are you reporting a crash? Please attach the crash log. Instructions at https://gitlab.com/gnachman/iterm2/wikis/crash-logs
Detailed steps to reproduce the problem:
- wait for a Broken Pipe error
What happened: Sometimes the internet in my building drops and when this happens all my iTerm windows print "Broken pipe", which at this point I must CTRL-C on each window before I press the Up Arrow then Enter restart the last command. I would like to automate this process to do the following actions whenever "Broken pipe" prints: CTRL-C, Up-Arrow, Enter. I've hit a wall trying to implement this idea.
The broken pipe message is printed internally and can't be caught by a trigger.
What should have happened: Allow the broken pipe message to be caught by a trigger OR allow user to choose an auto response to a broken pipe.