rm - bug or user error?

[Michael Webb]

Hello,

This is just a nit I discovered, but I thought I'd pass it along.

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.

From the man page:

    -f, --force
          ignore nonexistent files, never prompt

I suspect the "No match" is coming from the command line parsing and not 
rm itself.  However, the message starts with rm.

- Mike