Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-crg!nike!ucbcad!ucbvax!hplabs!tektronix!tekgen!tektools!jerryp
From: jerryp@tektools.UUCP (Jerry Peek)
Newsgroups: net.unix-wizards
Subject: Re: setenv problem in C-shell
Message-ID: <1427@tektools.UUCP>
Date: Tue, 2-Sep-86 10:36:34 EDT
Article-I.D.: tektools.1427
Posted: Tue Sep  2 10:36:34 1986
Date-Received: Wed, 3-Sep-86 18:43:09 EDT
References: <3454@brl-smoke.ARPA>
Reply-To: jerryp@tektools.UUCP (Jerry Peek)
Followup-To: net.unix
Organization: Tektronix, Inc., Beaverton, OR.
Lines: 27

[Doesn't this belong in net.unix -- instead of unix-wizards?]

In article <3454@brl-smoke.ARPA> DU>@brl-smoke.ARPA writes:
> You're probably going to hear this a lot...

and this is probably the 200th article that'll be posted, but I hate to see
errors posted to the net without corrections...

> You should do:
> 
> set noglob; eval `tset ... `

Not just that!  Don't forget to do "unset noglob" -- otherwise, the shell
won't expand filename wildcard characters afterwards.  Do this:

	set noglob; eval `tset ...`; unset noglob

(The wildcard characters, by the way, are almost certainly what's causing
your problem.  The "tset" command is probably spitting out * or ? or [ ]
characters, which expand into filenames, which screw up the contents of
the TERM or TERMCAP enviornment variables... and make them too long.)

--Jerry Peek, Tektronix, Inc.
US Mail:    MS 74-900, P.O. Box 500, Beaverton, OR 97077
uucp:       {allegra,decvax,hplabs,ihnp4,ucbvax}!tektronix!tektools!jerryp
CS,ARPAnet: jerryp%tektools@tektronix.csnet
Phone:      +1 503 627-1603