From e1fe79a9e705e3cab8f632cdbe8e1774cdef2761 Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Thu, 19 Feb 2015 04:13:20 +0000 Subject: - exit code overhaul: forx, forbacktickx, loopwhilex, if, ifelse, ifte, ifthenelse - new -o option to forx, forbacktickx, loopwhilex - documentation updated - version: rc for 2.1.0.0 --- doc/foreground.html | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) (limited to 'doc/foreground.html') diff --git a/doc/foreground.html b/doc/foreground.html index a2a465f..c0928e9 100644 --- a/doc/foreground.html +++ b/doc/foreground.html @@ -37,7 +37,8 @@ executes it, then waits for it to complete.
  • foreground sets the ? environment variable to the exit code of prog1. If prog1... -did not exit normally, the ? value is 111.
    • +was killed by a signal, the ? value is 256 plus the signal +number.
  • foreground then execs into prog2....
    • @@ -51,6 +52,12 @@ wrap external commands that exit instead of natively supporting the
  • foreground prog1... "" prog2... is equivalent to sh -c 'prog1... ; exec prog2...'.
    • +
  • 256 and above are not valid exit codes for commands, so when the +? environment variable contains 256 or more, it means that the +previous command was killed by a signal. There is no ambiguity here, and +? reports exactly what happened to the previous command; +foreground does not exit, so there is no need for +exit code approximation.
    • -- cgit v1.3.1