Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Keep CTRL+C propagated as signal and not as input #21

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ValentinTrinque
Copy link

According to the Windows documentation (https://learn.microsoft.com/en-us/windows/console/ctrl-c-and-ctrl-break-signals)

The SetConsoleMode function can disable the ENABLE_PROCESSED_INPUT input mode
for a console's input buffer, so CTRL+C is reported as keyboard input rather
than as a signal.

In the windows implementation, we do:

var newMode uint32
newMode &^= windows.ENABLE_ECHO_INPUT
newMode &^= windows.ENABLE_LINE_INPUT
newMode &^= windows.ENABLE_MOUSE_INPUT
newMode &^= windows.ENABLE_WINDOW_INPUT

newMode &^= windows.ENABLE_PROCESSED_INPUT // This reports CTRL+C as an input rather than as a signal.

newMode |= windows.ENABLE_EXTENDED_FLAGS
newMode |= windows.ENABLE_INSERT_MODE
newMode |= windows.ENABLE_QUICK_EDIT_MODE

It should be changed to newMode |= windows.ENABLE_PROCESSED_INPUT so we keep the signal propagation.

According to the Windows documentation (https://learn.microsoft.com/en-us/windows/console/ctrl-c-and-ctrl-break-signals)

> The SetConsoleMode function can disable the ENABLE_PROCESSED_INPUT input mode
> for a console's input buffer, so CTRL+C is reported as keyboard input rather
> than as a signal.

In the windows implementation, we do:

```go
var newMode uint32
newMode &^= windows.ENABLE_ECHO_INPUT
newMode &^= windows.ENABLE_LINE_INPUT
newMode &^= windows.ENABLE_MOUSE_INPUT
newMode &^= windows.ENABLE_WINDOW_INPUT

newMode &^= windows.ENABLE_PROCESSED_INPUT // This reports CTRL+C as an input rather than as a signal.

newMode |= windows.ENABLE_EXTENDED_FLAGS
newMode |= windows.ENABLE_INSERT_MODE
newMode |= windows.ENABLE_QUICK_EDIT_MODE
```

It should be changed to `newMode |= windows.ENABLE_PROCESSED_INPUT` so we keep the signal propagation.
@ValentinTrinque
Copy link
Author

Is this project still maintained ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant