doc: move signal 0 out of Signal Events list#62207
Open
kovan wants to merge 1 commit intonodejs:mainfrom
Open
Conversation
Signal `0` is not a signal that can be listened for via process.on() — it is only meaningful when sent via process.kill() to test process existence. Move it out of the signal events list (which documents signals that can be received) and add a brief cross-reference to process.kill() where it is already documented. Fixes: nodejs#42287 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
nodejs-github-bot
added
doc
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Signal
0is not a signal that can be listened for viaprocess.on()— it is only meaningful when sent viaprocess.kill()to test for process existence. Remove it from thesignal events bullet list (which documents receivable signals) and
the Windows emulation list, replacing both with a brief
cross-reference to
process.kill()where signal0is alreadydocumented.
Verified:
process.on(0, ...)/process.on('0', ...)does notregister a signal handler. The
process.kill()docs at the samepage already document signal
0behavior.Fixes: #42287