Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83; site cbosgd.UUCP
Path: utzoo!linus!vaxine!wjh12!genrad!decvax!harpo!eagle!mhuxl!ihnp4!cbosgd!mark
From: mark@cbosgd.UUCP (Mark Horton)
Newsgroups: net.bugs.4bsd
Subject: Re: 4.xBSD /bin/csh bug fix wanted.. - (nf)
Message-ID: <959@cbosgd.UUCP>
Date: Sun, 12-Feb-84 22:23:21 EST
Article-I.D.: cbosgd.959
Posted: Sun Feb 12 22:23:21 1984
Date-Received: Wed, 15-Feb-84 00:32:33 EST
References: <1569@pur-ee.UUCP>
Organization: AT&T Bell Laboratories, Columbus
Lines: 15

It's not a bug in csh, it's a misfeature of eval.  You're supposed to
invoke tset like this
	set noglob
	eval `tset -s ....`
Even though tset outputs "set noglob" at the beginning, it doesn't do
any good because the line is scanned before the first set is done.
(It says so on the tset manual page, which I wish people would read
before reporting this "bug".)

This only matters for terminals that have shell special characters
in their termcaps, such as *.

The "every other time" behaviour happens because on the alternate
times, noglob is being set (and left set since the 2nd part bombs
out before it can be cleared) and then cleared (when it works fine).