Problems with rm -f

[Neil Rickert]

In article <1991May14.190816.17169 at rodan.acs.syr.edu> jstewart at rodan.acs.syr.edu (Ace Stewart) writes:
>Problem: When running a "rm -f" on files that may or may not be in a
>sub-directory, the -f doesn't seem to suppress the error output if a
>file doesn't exist. Script as follows:
>
>% rm -f .Mail/drafts/,*			Do it again, _problems!_
>No match.
>%

  That message is not coming from 'rm'.  It is coming from your shell,
probably /bin/csh.  When you use '*' in a command, you are asking the shell
to expand '*' into a list of matching file names.  Here it is just telling
you that there were not matching names.  If the message bothers you, try
'set nonomatch' to see if this turns it off.  Or use a different shell.

-- 
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
  Neil W. Rickert, Computer Science               <rickert at cs.niu.edu>
  Northern Illinois Univ.
  DeKalb, IL 60115                                   +1-815-753-6940