Bug 10665 - no delete key in redhat 6.2
Summary: no delete key in redhat 6.2
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: termcap
Version: 6.2
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Bernhard Rosenkraenzer
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2000-04-08 17:36 UTC by jszabo
Modified: 2016-10-28 01:26 UTC (History)
0 users

Clone Of:
Last Closed: 2000-04-08 17:42:07 UTC

Attachments (Terms of Use)

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.


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.


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

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

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