Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxn!ihnp4!houxm!whuxl!whuxlm!akgua!gatech!seismo!brl-adm!brl-smoke!smoke!mwm%ucbopal@ucbvax.berkeley.edu
From: mwm%ucbopal@ucbvax.berkeley.edu
Newsgroups: net.unix-wizards
Subject: Re: job control
Message-ID: <84@brl-smoke.ARPA>
Date: Thu, 17-Apr-86 11:34:48 EST
Article-I.D.: brl-smok.84
Posted: Thu Apr 17 11:34:48 1986
Date-Received: Mon, 21-Apr-86 02:06:25 EST
Sender: news@brl-smoke.ARPA
Lines: 18

> It's somewhat distressing to hear that I have to know what sort of
> Unix system I'm on so I don't use "env" when I should use "printenv".
> I would be a lot happier if I heard that "printenv TERM" would work as
> a replacement for "echo $TERM".

Uh, sorry, Mark, but which of env/printenv/echo works depends on what
command line interpreter you're using, as well as what Unix you're
using. Just ask how to find the terminal type on a v6 system :-).

The ability to use your favorite CLI is a win. You have to expect that
things that change/print/otherwise-diddle the internal data structures
of the CLI will change as you change CLIs. For the most part, they
stay constant across different flavors of Unix if you stay with the
same CLI. Now, what you shouldn't ask is how the terminal type
information got imbedded into the CLI on Unix.

	"Unix is rapidly replacing obsolete 10 to 15 year old OS's."
	<mike