Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!uunet!bcstec!galileo!rfh3273
From: rfh3273@galileo.rtn.ca.boeing.com (Dick Harrigill)
Newsgroups: comp.sys.apollo
Subject: Re: TERM Variable at 10.3
Message-ID: <262@galileo.rtn.ca.boeing.com>
Date: 4 Feb 91 20:42:21 GMT
Organization: be30r
Lines: 34

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 .RC and startup files that
I used with 10.2, so I can't trace it to something I have done differently.

Before making this post, I called the HP 800-2APOLLO hotline. 
The person I spoke with (I believe Hal Jones??) apparently tried 
this on several HP machines and verbally verfied that this
was indeed the case, and that it seems to have been introduced
at 10.3.  There is, however, obviously something else going on here.
 
Again, I am not advocating that looking at TERM is the best
(or even a good) way to identifiy the screen type.  I am
simply acknowledging the fact that there are programs and
scripts in existance that use this method and may no longer work.

Oh well, this was the first post I did on the usenet; for
me its purpose was mainly to verify whether or not I was
getting out while at the same time expressing an item
of possible interest.  Seems it works....  Thanks for the replies.

 -Dick

-- 
Dick Harrigill, an independent voice from:     Boeing Commercial Airplanes 
M/S 9R-49  PO BOX 3707                       Renton Avionics/Flight Systems
Seattle, WA  91824                                  Computing Support
(206) 393-9539     rfh3273@galileo.rtn.ca.boeing.com