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/forx.html | 16 +++++++++++-----
1 file changed, 11 insertions(+), 5 deletions(-)
(limited to 'doc/forx.html')
diff --git a/doc/forx.html b/doc/forx.html
index 0349a85..0ed4799 100644
--- a/doc/forx.html
+++ b/doc/forx.html
@@ -28,7 +28,7 @@
- forx [ -p | -x breakcodes ] variable { args... } loop...
+ forx [ -p | -o okcodes | -x breakcodes ] variable { args... } loop...
@@ -48,11 +48,17 @@ That block contains a list of args.
loop... to exit before spawning the next one. forx
will still wait for all instances of loop to terminate before
exiting, though.
- - -x breakcodes : breakcodes must
+
- -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 breakcodes,
-forx will not run the following instances of the loop, but exit immediately with the
-same exit code.
+hasn't been given and loop exits with one of the codes in
+okcodes,
+forx will run the following instances of the loop, but if the exit code is
+not listed in okcodes, forx 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 forx break the loop and exit, and the unlisted exit
+codes will make it keep looping.
Notes
--
cgit v1.2.3