Expected Behavior
When pressing Ctrl+Pause/Break, the INT is sent to running application.
Actual Behavior
The tab closes and bash never sees the INT from Ctrl+Pause/Break.
Steps to reproduce
- Set up Console to run bash.exe
- Press Ctrl+Pause/Break
If I run bash.exe directly, this code in the .bashrc will be triggered on both Ctrl+C and Ctrl+Pause/Break and the bash window never closes. In console, only Ctrl+C triggers the code and Ctrl+Pause/Break immediately closes the tab.
trap ctrl_break INT
function ctrl_break() {
echo "** Trapped CTRL-BREAK"
}
I am seeing this issue because there is an application I use that ignores Ctrl+C but instead only listens for Ctrl+Pause/Break to exit early.
Expected Behavior
When pressing Ctrl+Pause/Break, the INT is sent to running application.
Actual Behavior
The tab closes and bash never sees the INT from Ctrl+Pause/Break.
Steps to reproduce
If I run bash.exe directly, this code in the .bashrc will be triggered on both Ctrl+C and Ctrl+Pause/Break and the bash window never closes. In console, only Ctrl+C triggers the code and Ctrl+Pause/Break immediately closes the tab.
I am seeing this issue because there is an application I use that ignores Ctrl+C but instead only listens for Ctrl+Pause/Break to exit early.