Hide Forgot
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
Created attachment 921770 [details] Reintroduce $anyerror as is done in upstream
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
I tried to wait until 6.19 release but it was postponed, so fixing the issue for f21+: http://pkgs.fedoraproject.org/cgit/tcsh.git/commit/?id=804e62644c28b1e4aea8
Well, I swapped bz numbers in my head, reopening. The patch from comment #4 is reusable in RHEL7. QA: test case added
Created attachment 1050655 [details] Proposed bugfix
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-2431.html