RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1334312 - zsh _arguments function not working
Summary: zsh _arguments function not working
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: zsh
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Kamil Dudka
QA Contact: Jan Kepler
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-09 11:32 UTC by Marko Myllynen
Modified: 2016-11-03 23:03 UTC (History)
3 users (show)

Fixed In Version: zsh-5.0.2-21.el7
Doc Type: Bug Fix
Doc Text:
needless to document IMO
Clone Of:
: 1350432 (view as bug list)
Environment:
Last Closed: 2016-11-03 23:03:16 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2152 0 normal SHIPPED_LIVE zsh bug fix update 2016-11-03 13:13:01 UTC

Description Marko Myllynen 2016-05-09 11:32:15 UTC
Description of problem:
I'm seeing an issue with the _arguments utility function on RHEL 7.2, below is a minimal test case:

#compdef foo

_arguments -S -s -w \
    '(- *)'{-h,--help}'[display help information]' \
    '(- *)'{-V,--version}'[print program version]' \
    "(-t --test)"{-t,--test}'[test]' \
    && return 0

Then when using it we see the issue:

$ foo <TAB>
--help     -h  -- display help information                                    
--test     -t  -- test                                                        
--version  -V  -- print program version                                       
-w
$ foo --help

So the "-w" parameter leaks through. There's an upstream fix available for this already I verified that it indeed fixed the issue for me as well:

756526eef3e064c3ffb023ae5e5e6df42e6e9162

Could this be backported to RHEL 7 as well?

PS. While at it, perhaps also consider 2810317ae2f2f96d06add76c17510a90f2ea3f62 for _arguments as well.

Thanks.

Version-Release number of selected component (if applicable):
zsh-5.0.2-20.el7.x86_64

Comment 2 Kamil Dudka 2016-05-09 13:26:27 UTC
Thank you for the analysis!  I am fine with picking both the upstream commits if the bug gets approved for inclusion.

Comment 9 errata-xmlrpc 2016-11-03 23:03:16 UTC
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-2016-2152.html


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