Bug 3509 - xterm terminal definition does not work properly
xterm terminal definition does not work properly
Status: CLOSED DUPLICATE of bug 2639
Product: Red Hat Linux
Classification: Retired
Component: termcap (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Preston Brown
: 3785 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 1999-06-16 15:59 EDT by rcarpen
Modified: 2008-05-01 11:37 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-01-18 15:26:08 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 rcarpen 1999-06-16 15:59:36 EDT
When telnetting form a Solaris xterm to RH6.0 machine,
fullscreen programs such as tin,pico,pine do not function
properly.  All test is set to reverse mode, and ^O fails to
Comment 1 Jeff Johnson 1999-08-21 13:10:59 EDT
*** Bug 3785 has been marked as a duplicate of this bug. ***

there is a problem with term=xterm when connecting from
a solaris7 machine.  to reproduce the problem, simply
log in from a solaris7 xterm to a redhat 6 system and then
do (for example) man tcsh.  the hightlights and underlines
are completely messed up.  another annoyance:  "less" leaves
the terminal with reverse video highlihts.

set term=xterm-color

fixes the problem.

this worked fine under redhat5.2 to the same solaris7 host.
Comment 2 rcarpen 1999-08-30 14:16:59 EDT
set term=xterm-color does fix the display problems.  Can we fix the
source of this problem though?  It is not fun to configure every
server to set term=xterm-color.  Also,  ^O still does not work in
pine, pico, and other fullscreen apps.
Comment 3 hawkfan 1999-10-05 16:56:59 EDT
This looks like a dup of bug #2639, can somone fix this already??  All
the world is _NOT_ XFree86.
Comment 4 Preston Brown 2000-01-18 15:26:59 EST
*** This bug has been marked as a duplicate of 2639 ***

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