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

Jump to bottom

Handling of the CTRL+C signal is not consistent across platforms #36

Closed
OJ opened this issue Oct 19, 2016 · 2 comments
Closed

Handling of the CTRL+C signal is not consistent across platforms #36

OJ opened this issue Oct 19, 2016 · 2 comments
Assignees
@OJ
Labels
bug

Comments

@OJ
Copy link
Owner

OJ commented Oct 19, 2016

I'm seeing this behave strangely in different contexts, and so I might just remove it until I figure out what is going on. OSX seems to be the strangest.
@OJ OJ added the bug label Oct 19, 2016
@OJ OJ self-assigned this Oct 19, 2016
@rverton
Copy link
Contributor

rverton commented Oct 24, 2016

What strange behaviour did you observe? I have no problems with CTRL+C under OSX. I read that sometimes there are problems with catching signals when running via go run, but I have no problems doing it this way, too.

The docs also say os.Interrupt is available on all systems.

@OJ
Copy link
Owner Author

OJ commented Aug 27, 2018

Should be good now.

@OJ OJ closed this as completed Aug 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@OJ OJ

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@OJ @rverton