csh and tset
utzoo!decvax!cca!hplabs!hao!menlo70!sytek!zehntel!teklabs!terryl at sri-unix
utzoo!decvax!cca!hplabs!hao!menlo70!sytek!zehntel!teklabs!terryl at sri-unix
Thu Sep 16 00:32:50 AEST 1982
Actually, nothing that you noted about that way eval works with tset
is entirely correct. If you look at the man page for tset, it says there
is a bug in the way the csh does evals, and the correct way to do a tset is:
set noglob
eval `tset [blah] [blah] ...`
The reason the tset works is that the shell variable noglob stays set
after the first eval. Doing a second eval does not do any file name expansion
because noglob is set from the first eval. The actual bug is that file name
expansion is done by eval before command execution (or some other nonsense
like that). I don't think the TERMCAP environment variable has anything to
do with it.
Terry Laskodi
{dec,ucb}vax!teklabs!terryl (UUCP)
or
terryl at tektronix (CSNET)
or
terryl.tektronix at udel-relay (ARPA)
More information about the Comp.bugs.2bsd
mailing list