Mailinglist Archive: opensuse (1377 mails)
| < Previous | Next > |
RE: [S.u.S.E. Linux] xterm problem: unwanted highlighting in rev
- From: Ted.Harding@xxxxxxxxxxxxxxxx ((Ted Harding))
- Date: Sun, 09 Aug 1998 11:48:57 +0100 (BST)
- Message-id: <XFMail.980809114857.Ted.Harding@xxxxxxxxxxxxxxxx>
On 09-Aug-98 Joan Bresnan wrote:
> I seem to have a problem with xterm in my new SuSE linux 5.2
> installation that I can't solve. The problem is that when I run an
> xterm and use more/less, the first pageful of text is normal, and the
> second appears in reverse video. The reverse video disappears when I
> quit more/less and do "ls". This problem does not occur with rxvt. But
> I would like to be able to use xterm, so I've looked around for clues on
> the problem by reading the man pages and app-defaults for xterm and
> rxvt, looking at .Xresources, /etc/inputrc, etc., and reading the
> archives of the suse-linux-e list. Unfortunately, nothing I have tried
> seems to work.
>
> Can anyone suggest a clue or solution?
I once hit a similar problem (when trying out a commercial X): going over the
end of page in "less" put the whole xterm permanently in reverse video.
I can only offer a pointer. The root of the problem lies in the effect that
various escape sequences for terminal control have on the behaviour of xterm
(and "less" uses excape sequences heavily). You need to be looking at
/etc/termcap, and possibly at curses/ncurse, and at how your X (and xterm) use
these.
The mechanism in "less" is that the status-line at the bottom of the xterm is
in reverse video, initiated by an escape sequence. Normally an escape sequence
sent at the end of the status line should cancel reverse video. For some reason,
this is not being properly responded to, and it stays in reverse video. If you
can't solve the problem at the level of the basic reason,
The normal (e.g. XF96_SVGA of XF86_VGA16) drivers in XFree86 should not cause
this problem in S.u.S.E.-5.2, according to my experience with installing this.
Are you using a special X driver?
In your xterm, enter "echo $TERM". The response should be "xterm". If not, this
might be the source of the trouble (though I've no idea how that situation
might arise). If that is OK, check /etc/termcap for the "xterm" entry.
Sorry I can't help more specifically.
Ted.
--------------------------------------------------------------------
E-Mail: (Ted Harding) <Ted.Harding@xxxxxxxxxxxxxxxx>
Date: 09-Aug-98 Time: 11:48:57
--------------------------------------------------------------------
-
To get out of this list, please send email to majordomo@xxxxxxxx with
this text in its body: unsubscribe suse-linux-e
| < Previous | Next > |