Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 647524 - completion after an environment variable results in a "bad substitution" error
completion after an environment variable results in a "bad substitution" error
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: ksh (Show other bugs)
5.5
Unspecified Unspecified
medium Severity medium
: rc
: ---
Assigned To: Michal Hlavinka
qe-baseos-tools
: Patch
Depends On:
Blocks: 702015
  Show dependency treegraph
 
Reported: 2010-10-28 12:52 EDT by Jeff Bastian
Modified: 2012-02-21 00:50 EST (History)
3 users (show)

See Also:
Fixed In Version: ksh-20100621-1.el5
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 702015 (view as bug list)
Environment:
Last Closed: 2012-02-21 00:50:21 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
filename completion patch (525 bytes, patch)
2010-10-28 12:52 EDT, Jeff Bastian
no flags Details | Diff


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0159 normal SHIPPED_LIVE ksh bug fix and enhancement update 2012-02-20 09:53:47 EST

  None (edit)
Description Jeff Bastian 2010-10-28 12:52:16 EDT
Created attachment 456294 [details]
filename completion patch

Description of problem:
Filename completion with M-= (or ESC =) after an environment variable fails with a "bad substitution" error:
   $ ksh
   $ set -o emacs
   $ grep $i ESC =
   ksh: ${!i @}: bad substitution

It does not matter if $i is set or not.
   $ ksh
   $ set -o emacs
   $ export i=1
   $ grep $i ESC =
   ksh: ${!i @}: bad substitution

An upstream patch from Siddhesh Poyarekar fixes this bug.
   https://mailman.research.att.com/pipermail/ast-developers/2010q4/000795.html
   https://mailman.research.att.com/pipermail/ast-developers/2010q4/000796.html

Version-Release number of selected component (if applicable):
ksh-20100202-1.el5_5.1

How reproducible:
every time

Steps to Reproduce:
1. ksh
2. set -o emacs
3. grep $i ESC =
  
Actual results:
ksh: ${!i @}: bad substitution

Expected results:
list of filenames

Additional info:
Comment 2 Michal Hlavinka 2010-10-29 02:57:57 EDT
thanks, reproducible
Comment 3 RHEL Product and Program Management 2011-01-11 16:09:22 EST
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.
Comment 4 RHEL Product and Program Management 2011-01-11 17:45:08 EST
This request was erroneously denied for the current release of
Red Hat Enterprise Linux.  The error has been fixed and this
request has been re-proposed for the current release.
Comment 5 RHEL Product and Program Management 2011-05-31 09:44:52 EDT
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.
Comment 8 errata-xmlrpc 2012-02-21 00:50:21 EST
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.

http://rhn.redhat.com/errata/RHBA-2012-0159.html

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