We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It looks like the main signal handler is still the main process, not the subshell process.
SIGQUIT in this example should quit the entire subshell, not just cat:
SIGQUIT
(cat || echo 123)
We still print 123 in this example.
123
This issue also causes (cat) | (cat) to print too many newlines when Ctrl+C.
(cat) | (cat)
This also makes it apparent: (cat || echo 1 && exit 2) || echo $?
(cat || echo 1 && exit 2) || echo $?
(((cat)))
The text was updated successfully, but these errors were encountered:
Ctrl+C
Options to handle the main process differently:
Sorry, something went wrong.
No branches or pull requests
It looks like the main signal handler is still the main process, not the subshell process.
SIGQUIT
in this example should quit the entire subshell, not just cat:We still print
123
in this example.This issue also causes
(cat) | (cat)
to print too many newlines when Ctrl+C.This also makes it apparent:
(cat || echo 1 && exit 2) || echo $?
(((cat)))
also prints another newline for every subshell. - [BUG] minishell running in minishell prints too many newlines after exiting, also in subshells #257The text was updated successfully, but these errors were encountered: