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

Use stty interrupt setting instead of hardcoding Ctrl+C #31

Open
crabdancing opened this issue Sep 23, 2024 · 0 comments
Open

Use stty interrupt setting instead of hardcoding Ctrl+C #31

crabdancing opened this issue Sep 23, 2024 · 0 comments

Comments

@crabdancing
Copy link

crabdancing commented Sep 23, 2024

I have the following stty config:

speed 38400 baud; line = 0;
intr = ^Q; susp = ^W;
-brkint -imaxbel

The key issue here is that interrupt is set to Ctrl+Q. Raw terminal apps will (hopefully) pick up on this and interrupt on Ctrl+Q instead of Ctrl+C. promkit does not do this however. Instead, it ONLY responds to Ctrl+C.

@crabdancing crabdancing changed the title Use stty interrupt instead of hardcoding Ctrl+C Use stty interrupt setting instead of hardcoding Ctrl+C Sep 23, 2024
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

No branches or pull requests

1 participant