https://bugs.winehq.org/show_bug.cgi?id=55197
--- Comment #5 from Eric Pouech eric.pouech@gmail.com ---
Should wine run the CTRL_CLOSE_EVENT handler then CTRL+\ is pressed (or SIGQUIT is pressed)?
what I meant in comment #3 is that adding support for passing back to handler the various events will require an important rewrite of that part, and I'm not sure it'll happen soon (for the detail, the ctrl-c (resp ctrl-break or ctrl-) from windows world are passed to process in the process groups with kill SIGTERM (resp SIGQUIT). this has the following limitations: - hard to add more events (like CTRL_CLOSE_EVENT) as signal as no parameter - impossible to discriminate between console generated event => unix signal and other internal use (like kernel32.TerminateProcess()) to it'll require to put in place another channel to send console event to process. don't hold your breath on that feature.