From 639ea3caa01bb3dda0f6fc75c032929a5f2dab09 Mon Sep 17 00:00:00 2001 From: Soumya Date: Fri, 3 Apr 2020 10:04:16 -0700 Subject: [PATCH] Update docs for `fish_kill_signal`, use "job" rather than "command" --- CHANGELOG.md | 2 +- doc_src/index.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 9d6fa31d3..ef1fd11ab 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -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 diff --git a/doc_src/index.rst b/doc_src/index.rst index 8ba942b4c..321ec0d6e 100644 --- a/doc_src/index.rst +++ b/doc_src/index.rst @@ -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.