CONTROL+C on close instead of CONTROL_CLOSE_EVENT

[jredfox]

Description of the new feature/enhancement

on closing the x button send a control+c signal to all processes by default instead of terminating them. Definition: the x button is described as both the x button for windows terminal itself and every tab

Proposed technical implementation details (optional)

there are three ways to implement this maybe make them all options

• Send Control+C signal and do nothing if processes don't respond. If nothing is done then the user clicks the X button a second time send a SIGTERM(CONTROL_CLOSE_EVENT) that gives the application 5s to respond before closing
• Send Control+C signal and do nothing for 5-8s, After that prompt the user if they are sure they want to kill all processes inside before closing like macOs but not immediate as we want CLI programs to try and save on regular shutdown
• Add an option to always use Control_CLOSE_EVENT (SIGTERM) on X button for those users that don't want the prompt and don't care about data loss / file corruption

[lhecker]

Could you clarify why this is feature would be important to you? It would help us give this feature request a priority.

[jredfox]

important

Most console apps using cli's are running important functions and will have file corruption if it's forcibly terminated. Always using the windows equivalent of SIGTERM isn't a good default solution it should be an opt in option not the only option.

[lhecker]

But SIGTERM is the soft exit equivalent under UNIX. Did you mean SIGQUIT? That one forcibly terminates. CONTROL_CLOSE_EVENT is a little bit like SIGTERM's usage in upstart and systemd, because it sends an exit signal but has a timeout of 5s until it sends an equivalent of SIGQUIT. It's very similar under UNIX when a service management software is being used. I do understand what you mean however, so I'll bring it up for discussion.

[lhecker]

Woops commented on the wrong issue. 😄