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

Signals SIGTSTP / SIGCONT not properly handled #835

Open
gwenn opened this issue Dec 25, 2024 · 3 comments
Open

Signals SIGTSTP / SIGCONT not properly handled #835

gwenn opened this issue Dec 25, 2024 · 3 comments

Comments

@gwenn
Copy link
Collaborator

gwenn commented Dec 25, 2024

To reproduce:

  1. cargo run --example minimal
  2. from an other shell killall -TSTP minimal
  3. from the original shell, fg

At step 3, we expect the prompt to be redrawn but nothing happen.

@gwenn
Copy link
Collaborator Author

gwenn commented Jan 5, 2025

To avoid duplicating code, we should reuse the same handler / pipe for all signals.
Like fish-shell
and mortal.
But signal-hook prevents it...

@gwenn gwenn mentioned this issue Jan 26, 2025
4 tasks
@gwenn
Copy link
Collaborator Author

gwenn commented Jan 27, 2025

I've tried to handle SIGTSTP signal but that didn't work.
I've also tried to handle SIGCONT signal without success.

@gwenn
Copy link
Collaborator Author

gwenn commented Feb 3, 2025

For SIGTSTP, maybe try to call the previous handler after restoring the original mode like isocline ?

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