[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: rm - bug or user error?
From: |
Alan Curry |
Subject: |
Re: rm - bug or user error? |
Date: |
Tue, 26 Jan 2010 20:52:45 -0500 (GMT+5) |
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
- rm - bug or user error?, Michael Webb, 2010/01/26
- Re: rm - bug or user error?,
Alan Curry <=
- Re: rm - bug or user error?, Jon Stanley, 2010/01/26
- Message not available
- Re: rm - bug or user error?, Jon Stanley, 2010/01/26
- Re: rm - bug or user error?, Alan Curry, 2010/01/26
- Re: rm - bug or user error?, Bob Proulx, 2010/01/26
- Re: rm - bug or user error?, Eric Blake, 2010/01/26
- Re: rm - bug or user error?, Michael Webb, 2010/01/26
Re: rm - bug or user error?, Eric Blake, 2010/01/26