Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 913570

Summary:	Default key bindings in /etc/screenrc do not supply kill region (remove) command
Product:	Red Hat Enterprise Linux 5	Reporter:	Miroslav Hradílek <mhradile>
Component:	screen	Assignee:	Petr Hracek <phracek>
Status:	CLOSED WONTFIX	QA Contact:	BaseOS QE - Apps <qe-baseos-apps>
Severity:	unspecified	Docs Contact:
Priority:	low
Version:	5.9	CC:	mhradile
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-03-07 12:52:09 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:

Description Miroslav Hradílek 2013-02-21 13:51:28 UTC

Description of problem:
Default configuration file /etc/screenrc redefines some key bindings for reasons. One of them is that (Ctrl+a x) (lock screen) is moved to (Ctrl+a X) which replaces default meaning (kill region) as described in manual page. Redefinitions in /etc/screenrc do not provide any alternative for (kill region).

Version-Release number of selected component (if applicable):
screen-4.0.3-4.el5

How reproducible:
Always

Steps to Reproduce:
1. "screen"
2. Ctrl+a S
3. Ctrl+a tab
4. Ctrl+a X
  
Actual results:
Locks screen

Expected results:
Kill new region

Additional info:
Shouldn't manual page reflect real defaults?

Comment 1 Petr Hracek 2013-03-07 12:52:09 UTC

I am sorry, but it is too late in the RHEL-5 release cycle [1].  At the moment we are addressing only critical and security related issues in RHEL-5.  This one is fixed in RHEL-6.  I am closing the bug as WONTFIX.

[1] https://access.redhat.com/support/policy/updates/errata/