csh script interruptability

[utzoo!decvax!harpo!utah-cs!utah-gr!thomas]

Re: cmd1 && cmd2 &

The reason that the csh waits for the first to finish is that & binds
more tightly than && (i.e., it only applies to cmd2, not to cmd1 && cmd2).
Putting it in () is indeed the correct thing to do.  Why it prints garbage
for the command name, I don't know, I've never had this problem.
=Spencer