summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorLaurent Bercot <ska-skaware@skarnet.org>2024-04-15 13:19:13 +0000
committerLaurent Bercot <ska@appnovation.com>2024-04-15 13:19:13 +0000
commita27fb6dae5142a4220549845ef31516757ae6e4a (patch)
treef93f39adcd3bd6dbb955c7d0e1623670b1908cd5 /doc
parenta5b7a319fb558f5df599de286318029d455ed193 (diff)
downloadexecline-a27fb6dae5142a4220549845ef31516757ae6e4a.tar.xz
Use more accurate exit codes in backtick and foreground
Signed-off-by: Laurent Bercot <ska@appnovation.com>
Diffstat (limited to 'doc')
-rw-r--r--doc/backtick.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/backtick.html b/doc/backtick.html
index 38c02a2..3081407 100644
--- a/doc/backtick.html
+++ b/doc/backtick.html
@@ -85,8 +85,8 @@ is set to <em>default</em>, and execution proceeds. </li>
If the command line can keep running after <em>prog1</em> crashes or exits
nonzero, i.e. if one of the <tt>-I</tt>, <tt>-x</tt> -or <tt>-D</tt> has been
given, then <tt>backtick</tt> also adds the <tt>?</tt> variable to the
-environment; it then contains an <a href="exitcodes.html">approximation</a>
-of <em>prog1</em>'s exit code.
+environment. If <em>prog1</em> exited normally, the variable contains its exit
+code; otherwise, 256 plus the number of the signal that killed it.
</p>
</body>