You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, when a signal is registered via the Signals type, the default signal handler is disabled. This requires the user to manually call the low-level signal handler. This is probably what's desired for most cases, like handling SIGINT, since the default signal handler for SIGINT ends the application. However, for other signals, it may be desired to call the default signal handler. I think there should be an option in add_signals or other to call the default signal handler on receipt.
The text was updated successfully, but these errors were encountered:
Right now, when a signal is registered via the
Signals
type, the default signal handler is disabled. This requires the user to manually call the low-level signal handler. This is probably what's desired for most cases, like handlingSIGINT
, since the default signal handler forSIGINT
ends the application. However, for other signals, it may be desired to call the default signal handler. I think there should be an option inadd_signals
or other to call the default signal handler on receipt.The text was updated successfully, but these errors were encountered: