Hide Forgot
+++ This bug was initially created as a clone of Bug #1123854 +++ IIRC upstream tcsh's git-log, from tcsh 6.17.06, the $anyerror variable works that way: $ echo $?anyerror 1 $ false | true ; echo $? 1 $ set anyerror ; false | true ; echo $? 1 $ unset anyerror ; false | true ; echo $? 0 From tcsh617.el5 we introduced (yet?) upstream-incompatible '$tcsh_posix_status' variable, which has opposite meaning. For compatibility with older RHEL and upstram, we need to support both 'anyerror' and 'tcsh_posix_status'. Currently, 'anyerror' variable is not working in RHEL7; where is tcsh-6.18.00. This bug exists to re-introduce $anyerror variable. References: bug 1025703, bug 759132 --- Additional comment from Pavel Raiskup on 2014-08-13 15:41:13 CEST --- JFTR, upstream is not interested in $tcsh_posix_status support: http://mx.gw.com/pipermail/tcsh-bugs/2014-July/000884.html Also, upstream has now clear documentation how $anyerror works: http://mx.gw.com/pipermail/tcsh-bugs/2014-July/000890.html ----- Fix is in original bugreport.
Fix including testcase for tcsh_posix_status pushed to Fedora (reusable in RHEL): http://pkgs.fedoraproject.org/cgit/tcsh.git/commit/?id=804e62644c28b1e4aea
Ignore comment #1 please -- I thought this bug is filed against RHEL7. This should be fixed in f21+.