Bug 187424 - bug / feature request: backport bind-tty-special-chars
Summary: bug / feature request: backport bind-tty-special-chars
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: bash
Version: 4.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Tim Waugh
QA Contact: Ben Levenson
Depends On:
TreeView+ depends on / blocked
Reported: 2006-03-30 20:29 UTC by William Yardley
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version: RHBA-2007-0680
Doc Type: Enhancement
Doc Text:
Clone Of:
Last Closed: 2007-11-15 15:57:27 UTC
Target Upstream Version:

Attachments (Terms of Use)
bash-bind-stty-chars.patch (2.16 KB, patch)
2007-05-18 09:00 UTC, Tim Waugh
no flags Details | Diff

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2007:0680 0 normal SHIPPED_LIVE bash bug fix and enhancement update 2007-11-14 16:32:15 UTC

Description William Yardley 2006-03-30 20:29:00 UTC
As noted on the bug-bash list, rebinding a character defined by stty is ignored
by bash v3.0. Bash 3.1 / readline 5.0 (5.1?) makes this a configurable option,
by setting:

set bind-tty-special-chars off

See also RH bug # 139384

(I have a couple posts about this as well, but they're not showing up in the
archive as of this moment).

I've tested, and this works with bash 3.1.x / readline 5.0 in FC5.

As my organization starts deploying RHEL 4 (vs 3), this is going to be a huge
annoyance. Is there any chance of backporting this feature, assuming the major
revision is unlikely to change within RHEL 4? If it matters, the company I work
for has a support contract.

Comment 3 Tim Waugh 2007-05-18 09:00:00 UTC
Created attachment 154983 [details]

This small patch seems to be the extent of it.

Comment 10 errata-xmlrpc 2007-11-15 15:57:27 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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