@@ -363,16 +363,11 @@ process.on('SIGINT', () => {
363
363
});
364
364
```
365
365
366
- * Note* : An easy way to send the ` SIGINT ` signal is with ` <Ctrl>-C ` in most
367
- terminal programs.
368
-
369
- It is important to take note of the following:
370
-
371
366
* ` SIGUSR1 ` is reserved by Node.js to start the [ debugger] [ ] . It's possible to
372
367
install a listener but doing so will _ not_ stop the debugger from starting.
373
368
* ` SIGTERM ` and ` SIGINT ` have default handlers on non-Windows platforms that
374
- resets the terminal mode before exiting with code ` 128 + signal number ` . If
375
- one of these signals has a listener installed, its default behavior will be
369
+ reset the terminal mode before exiting with code ` 128 + signal number ` . If one
370
+ of these signals has a listener installed, its default behavior will be
376
371
removed (Node.js will no longer exit).
377
372
* ` SIGPIPE ` is ignored by default. It can have a listener installed.
378
373
* ` SIGHUP ` is generated on Windows when the console window is closed, and on
@@ -383,7 +378,7 @@ It is important to take note of the following:
383
378
installed its default behavior will be removed.
384
379
* ` SIGTERM ` is not supported on Windows, it can be listened on.
385
380
* ` SIGINT ` from the terminal is supported on all platforms, and can usually be
386
- generated with ` CTRL +C` (though this may be configurable). It is not generated
381
+ generated with ` <Ctrl> +C` (though this may be configurable). It is not generated
387
382
when terminal raw mode is enabled.
388
383
* ` SIGBREAK ` is delivered on Windows when ` <Ctrl>+<Break> ` is pressed, on
389
384
non-Windows platforms it can be listened on, but there is no way to send or
@@ -934,10 +929,10 @@ process.exit(1);
934
929
935
930
The shell that executed Node.js should see the exit code as ` 1 ` .
936
931
937
- It is important to note that calling ` process.exit() ` will force the process to
938
- exit as quickly as possible * even if there are still asynchronous operations
939
- pending * that have not yet completed fully, * including* I/O operations to
940
- ` process.stdout ` and ` process. stderr` .
932
+ Calling ` process.exit() ` will force the process to exit as quickly as possible
933
+ even if there are still asynchronous operations pending that have not yet
934
+ completed fully, including I/O operations to ` process.stdout ` and
935
+ ` process.stderr ` .
941
936
942
937
In most situations, it is not actually necessary to call ` process.exit() `
943
938
explicitly. The Node.js process will exit on its own * if there is no additional
0 commit comments