Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!samsung!umich!terminator!pisa.ifs.umich.edu!rees
From: rees@pisa.ifs.umich.edu (Jim Rees)
Newsgroups: comp.sys.apollo
Subject: Re: TERM Variable at 10.3
Message-ID: <4fa27d98.1bc5b@pisa.ifs.umich.edu>
Date: 5 Feb 91 16:10:09 GMT
References: <262@galileo.rtn.ca.boeing.com>
Sender: usenet@terminator.cc.umich.edu (usenet news)
Reply-To: rees@citi.umich.edu (Jim Rees)
Organization: University of Michigan IFS Project
Lines: 14

In article <262@galileo.rtn.ca.boeing.com>, rfh3273@galileo.rtn.ca.boeing.com (Dick Harrigill) writes:

  I posted a notice last week about the TERM variable:
  >  At 10.3 this variable is always "apollo".  It is no longer set
  >  to a function of the screen type (e.g. apollo_1280_bw).
  I have since received several mail messages, most stating that they have
  not experienced this at their own site.  This is interesting because the
  TERM variable was indeed reset on my ring using 19"bw (1280bw), 330s (19l), 
  and 15" color (19l).  I am using the identacal [sic] .RC and startup files that
  I used with 10.2, so I can't trace it to something I have done differently.

Maybe that's your problem.  The startup files change from release to release,
and what you should do is merge any local changes you've made with changes
that Apollo has made.