Newsgroups: comp.sys.sgi
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!news.cs.indiana.edu!nstn.ns.ca!cs.dal.ca!silvert
From: silvert@cs.dal.ca (Bill Silvert)
Subject: Re: Mysterious notifier editable region -- identifying terminal
Message-ID: <1991Apr18.142713.4827@cs.dal.ca>
Sender: silvert@cs.dal.ca.UUCP (Bill Silvert)
Reply-To: silvert%biome@cs.dal.ca
Organization: Habitat Ecology Div., Bedford Inst. of Oceanography
References: <280B4213.363F@ibma0.cs.uiuc.edu> <1991Apr18.130802.7221@eagle.lerc.nasa.gov>
Distribution: na
Date: Thu, 18 Apr 91 14:27:13 GMT

In article <1991Apr18.130802.7221@eagle.lerc.nasa.gov> eddc@opus.lerc.nasa.gov (Dave Carek) writes:
>
>Do a man on launch to get more info.  BTW there's alot of other cool
>utilities in /usr/sbin you might want to check out.

There is some great stuff there, and I started to use launch and confirm
in shell scripts, until I realized that they wouldn't run if I logged in
from a dumb terminal.  Is there an easy way to determine whether the
terminal supports these various goodies other than a hack like a string
of case $TERM in ... followed by a list of acceptable terminal aliases?
If so, I could easily put together something like launch that invokes
/usr/sbin/launch only if it will run, otherwise giving me a dumb menu.
-- 
William Silvert, Habitat Ecology Division, Bedford Inst. of Oceanography
P. O. Box 1006, Dartmouth, Nova Scotia, CANADA B2Y 4A2.  Tel. (902)426-1577
UUCP=..!{uunet|watmath}!dalcs!biome!silvert
BITNET=silvert%biome%dalcs@dalac	InterNet=silvert%biome@cs.dal.ca