Michael Webb writes: > > I am within a directory containing directories dir1 and dir2 and *no* > files starting with f. > > shell> rm -rf dir1 dir2 f* > rm: No match. [...] > I suspect the "No match" is coming from the command line parsing and not > rm itself. However, the message starts with rm.
That's just how [t]csh reports non-matching globs: prefixed with the name of the command that wasn't run because of the error. This might help you figure out which line in a script had failed if you had multiple commands with globs. Since rm wasn't ever actually run, it had no influence on the format of the error message. -- Alan Curry
