Bug 1129703 - Tcsh does not support upstream's $anyerror variable
Summary: Tcsh does not support upstream's $anyerror variable
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: tcsh
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pavel Raiskup
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1123854
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-13 13:43 UTC by Pavel Raiskup
Modified: 2014-08-27 15:14 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1123854
Environment:
Last Closed: 2014-08-27 15:14:14 UTC


Attachments (Terms of Use)

Description Pavel Raiskup 2014-08-13 13:43:09 UTC
+++ 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.

Comment 1 Pavel Raiskup 2014-08-27 15:11:00 UTC
Fix including testcase for tcsh_posix_status pushed to Fedora (reusable in
RHEL):

http://pkgs.fedoraproject.org/cgit/tcsh.git/commit/?id=804e62644c28b1e4aea

Comment 2 Pavel Raiskup 2014-08-27 15:14:14 UTC
Ignore comment #1 please -- I thought this bug is filed against RHEL7.
This should be fixed in f21+.


Note You need to log in before you can comment on or make changes to this bug.