Bug 10665

Summary: no delete key in redhat 6.2
Product: [Retired] Red Hat Linux Reporter: jszabo
Component: termcapAssignee: Bernhard Rosenkraenzer <bero>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-04-08 17:42:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description jszabo 2000-04-08 17:36:35 UTC 
I couldn't find my report so I'm posting again to respond.

The delete key sends the code ^[[3~ instead of ^?.  On a fresh redhat 6.2
install delete does a delete forward in the local host.  However if I
telnet somewhere the delete beeps and makes a ~.  Same thing on my old
redhat machine that I upgraded a few versions to redhat 6.2 finally.  By
the way, I normally use zsh not bash.  Things seemed to have changed from
redhat 6.1.


Joe
Comment 1 Bernhard Rosenkraenzer 2000-04-08 17:42:59 UTC 
That's a feature. ;)
We modified the termcaps to be more consistent everywhere (get the same code no
matter whether you're on the console or in an xterm), eliminating the need for
some hacks.
The old termcaps are broken; there was no fully compatible way to fix this.
Possible fixes are updating the termcaps and ncurses libraries on the 6.1 box
and adding a ~/.termcap file on the 6.1 box.
Comment 2 jszabo 2000-04-08 17:53:59 UTC 
So basically if I don't make a binding for ^[[3~ in my current shell, I can't
use the delete key?

Can you tell me what to put in .termcap to make delete send a '^?' ?  Would be
cool for the backspace key too for that matter.


Joe
Comment 3 openshift-github-bot 2016-10-28 01:26:50 UTC 
Commit pushed to master at https://github.com/openshift/origin

https://github.com/openshift/origin/commit/86f064fc2f1dcc82d32b6d4ff31d1117e7806342
Display warning instead of error if ports 80/443 in use

Display warnings if ports 80 and/or 443 are already in use instead of an error,
as these ports are only needed for routing requests to the applications

Fixes issue #10665 and replaces pull request #10717