Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!rpi!uupsi!phage!monardo
From: monardo@cshl.org (Pat Monardo)
Newsgroups: comp.misc
Subject: Re: "Invalid null command"
Message-ID: <1991Apr2.172258.18851@cshl.org>
Date: 2 Apr 91 17:22:58 GMT
References: <1991Apr2.005620.11434@ico.isc.com>
Sender: news@cshl.org (NO MAIL)
Organization: Cold Spring Harbor Laboratory
Lines: 13

In article <1991Apr2.005620.11434@ico.isc.com> rcd@ico.isc.com (Dick Dunn) writes:
>
>Bourne shell users, accustomed to creating or emptying a file with a
>command like:
>	>splot
>or rewinding a tape with:
>	</dev/mt0
>are occasionally annoyed to find that csh rejects this syntax with the
>confusing message "Invalid null command".  (It is confusing because there
>is no such thing as a *valid* null command; attempts to find one will only
> end in frustration.)
;
i.e. a null command is valid if followed by a semicolon.