Bug 14354 - backspace problem with TERM=xterm-color
backspace problem with TERM=xterm-color
Product: Red Hat Linux
Classification: Retired
Component: screen (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Phil Copeland
Depends On:
  Show dependency treegraph
Reported: 2000-07-20 22:11 EDT by Need Real Name
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-12-07 17:26:20 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2000-07-20 22:11:04 EDT
as root on a 6.2 install

export TERM=xterm-color
echo ^V (then hit the backspace (^?, now a days))

It gets converted to "^[[3~"
Outside of screen this conversion does NOT take place.

This problem seems to be different than the ^H ^? dilemma
Comment 1 Derek Tattersall 2000-08-13 13:31:23 EDT
This problem still exiists in pinstrip RC1.
Comment 2 David Balažic 2000-08-25 04:04:40 EDT
using TERM=something when the real terminal is something-else
will always give you trouble :-)
What happens here is that when you press backspace a ^? code
is emitted ( at least on console and new xterms ), but this code
means nothing, according to xterm-color termcap entry ( kb is
defined as ^H there ).
But why screen converts it to ^[[3~ is beyond me.
screen probably need a good code clean-up.
^[[3~ is by-the-way usually the code for kD ( delete character
after cursor ), the Delete key .
Comment 3 Phil Copeland 2002-08-12 12:50:35 EDT
Just going through closing old non-issue bugs

(works fine with latest and greatest from rawhide, just recompile from the SRPM)


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