Subcmd exec and signal handling #1925
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
See the following commit
"No exit code" means a signal was delivered. Also don't exit with 0 anymore if input processing was interrupted (BrokenPipe).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
handle signals and SIGPIPE like other unix utils
"No exit code" means a signal was delivered. Also don't exit
with 0 anymore if input processing was interrupted (BrokenPipe).
misc small subcommand touch-ups
exec a subcommand directly if not writing to a terminal
main: switch subcommand and pager creation around
See the following commit
make stdout_is_term available in the config