Xref: utzoo alt.sys.sun:901 comp.windows.x:22479
Path: utzoo!attcan!uunet!samsung!zaphod.mps.ohio-state.edu!math.lsa.umich.edu!sharkey!msuinfo!pleiades.cps.msu.edu!raja
From: raja@bombay.cps.msu.edu (Narayan S. Raja)
Newsgroups: alt.sys.sun,comp.windows.x
Subject: Re: PROBLEM with xterm & telnet........help.......wedged screens....
Message-ID: <1990May29.025145.1648@msuinfo.cl.msu.edu>
Date: 29 May 90 02:51:45 GMT
References: <9005181226.AA09331@zit.cigy.> <100920217@hpcvlx.cv.hp.com> <1406@lectroid.sw.stratus.com>
Sender: news@msuinfo.cl.msu.edu
Reply-To: raja@cpsvax.cps.msu.edu (Narayan S. Raja)
Organization: Computer Science, Michigan State University, E. Lansing
Lines: 22


In article <1406@lectroid.sw.stratus.com>, (Farooq Butt) writes:

|> What's th' deal with telnet & xterm ?  Am I doing something dreadfully 
|> wring ? Why do the "r" tools work but telnet doesn't ????


When you "rsh" or "rlogin", the environment
variable "TERM" is always passed properly,
e.g. if you rlogin from an xterm the TERM on
the new host will still be "xterm".  This is
not the case with "telnet".  E.g., on occasion
when telnetting I found that TERM had been set
to "network".

Your problem should go away (I hope!) if you do
"SETENV TERM xterm" after telnetting.

Friendly regards,


Narayan Sriranga Raja.