Bug#610748: From the shell there is no way to adjust what problems cause an error

2011-03-03 Thread François Pinard
Le 2011-01-21 19:14, jida...@jidanni.org a écrit :

 From the shell there is no way to adjust what problems cause an error
 exit value. At least from reading (info (recode) Task level). Please
 add examples if there is a way.

Well, Recode has three settings for when to set the exit status.

The most lenient is activated with -f, in which case only system errors
or library mis-usage causes the exit status to be set.

By default, without -f nor -s, Recode sets the exit status as above, and
also in case of invalid or untranslatable input.  It also tries (but not
always succeed) to detect if output is going to be ambiguous at some
later recode-back time.

The most harsh is activated with -s, Recode then sets the exit code as
above, or if input is not canonically coded (and it also prevents itself
from completing recoding tables for making the recoding reversible).

I think these options are documented in the manual.  I also just added
the above notes in the Synopsis node.  If you have some more specific
need, please describe the problem you actually have.  Thanks!

François



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#610748: From the shell there is no way to adjust what problems cause an error

2011-01-21 Thread jidanni
X-debbugs-Cc: recode-b...@iro.umontreal.ca
Package: recode
Version: 3.6-17

From the shell there is no way to adjust what problems cause an error
exit value. At least from reading (info (recode) Task level). Please
add examples if there is a way.

Therefore one must do
$ recode . 2 err
$ grep recode: err  exit 1



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org