Update docs for fish_kill_signal, use "job" rather than "command"

This commit is contained in:
Soumya 2020-04-03 10:04:16 -07:00 committed by Johannes Altmanninger
parent 89c4ff9eae
commit 639ea3caa0
2 changed files with 2 additions and 2 deletions

View File

@ -3,7 +3,7 @@
## Notable improvements and fixes
- `fish --no-execute` will no longer complain about unknown commands or non-matching wildcards, as these could be defined differently at runtime (especially for functions). #977
- `jobs --quiet PID` will no longer print 'no suitable job' if the job for PID does not exist (e.g. because it has finished). #6809
- A variable `fish_kill_signal` will be set to the signal that terminated the last command, or `0` if the command exited normally.
- A variable `fish_kill_signal` will be set to the signal that terminated the last foreground job, or `0` if the job exited normally.
### Syntax changes and new commands

View File

@ -1062,7 +1062,7 @@ The user can change the settings of ``fish`` by changing the values of certain v
- ``pipestatus``, a list of exit statuses of all processes that made up the last executed pipe.
- ``fish_kill_signal``, the signal that terminated the previous command, or `0` if the command exited normally.
- ``fish_kill_signal``, the signal that terminated the last foreground job, or `0` if the job exited normally.
- ``USER``, the current username. This variable can be changed by the user.