Bug 1338689
Summary: | zsh exits with "parse error near `!'" for script with unescaped ! character | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Tim Speetjens <tspeetje> | ||||
Component: | zsh | Assignee: | Kamil Dudka <kdudka> | ||||
Status: | CLOSED ERRATA | QA Contact: | Jan Kepler <jkejda> | ||||
Severity: | high | Docs Contact: | Maxim Svistunov <msvistun> | ||||
Priority: | urgent | ||||||
Version: | 7.2 | CC: | fkrska, jkejda | ||||
Target Milestone: | rc | Keywords: | Patch, Regression, ZStream | ||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | zsh-5.0.2-23.el7 | Doc Type: | Bug Fix | ||||
Doc Text: |
*zsh* parses unescaped exclamation marks correctly now
Previously, *zsh* parser state was insufficiently initialized. Consequently, *zsh* failed to parse unescaped exclamation marks in a text string. With this update, *zsh* properly initializes the parser state. As a result, *zsh* now parses unescaped exclamation marks correctly.
|
Story Points: | --- | ||||
Clone Of: | |||||||
: | 1339601 (view as bug list) | Environment: | |||||
Last Closed: | 2016-11-03 23:03:20 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 1339601 | ||||||
Attachments: |
|
Description
Tim Speetjens
2016-05-23 09:37:06 UTC
This seems to be yet another regression introduced by the fix for bug #1241023. git-bisect points to the following (non-trivial) upstream commit as the fix for this bug: https://sourceforge.net/p/zsh/code/ci/cfd91eac Created attachment 1160672 [details]
[PATCH 2/7] Resolves: #1338689 - better initialize parser state
This fix is isolated out from a huge upstream commit that includes major
code refactoring changes together with the initialization fix actually
needed to resolve #1338689.
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 |