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/forbacktickx.html | 18 ++++++++++++------
1 file changed, 12 insertions(+), 6 deletions(-)
(limited to 'doc/forbacktickx.html')
diff --git a/doc/forbacktickx.html b/doc/forbacktickx.html
index d40799a..0780f3d 100644
--- a/doc/forbacktickx.html
+++ b/doc/forbacktickx.html
@@ -29,7 +29,7 @@ run another program.
- forbacktickx [ -p | -x breakcode ] [ -n ] [ -C | -c ] [ -0 | -d delim ] variable { gen... } loop...
+ forbacktickx [ -p | -o okcodes | -x breakcodes ] [ -n ] [ -C | -c ] [ -0 | -d delim ] variable { gen... } loop...
@@ -56,11 +56,17 @@ exiting, though.
- -0 : accept null characters from gen's output,
using them as delimiters. If this option and a -d option are
used simultaneously, the rightmost one wins.
- - -x breakcodes : breakcodes must
-be a comma-separated list of exit codes. If at some point loop...
-exits with a code listed in breakcodes, forbacktickx will not keep
-looping, but will exit immediately with the same exit code. This doesn't apply
-if the -p option has been given.
+ - -o okcodes : okcodes must
+be a comma-separated list of exit codes. If the -p flag
+hasn't been given and loop exits with one of the codes in
+okcodes,
+forbacktickx will run the following instances of the loop, but if the exit code is
+not listed in okcodes, forbacktickx will exit immediately with an
+approximation of the same exit code.
+ - -x breakcodes : like the previous
+option, but with inverted meaning - the listed exit codes are codes
+that will make forbacktickx break the loop and exit, and the unlisted exit
+codes will make it keep looping.
- Other options are used to control
the substitution mechanism for every x. Of course, you can't
split x.
--
cgit v1.3.1