Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!orstcs!ogicse!uwm.edu!linac!mp.cs.niu.edu!rickert
From: rickert@mp.cs.niu.edu (Neil Rickert)
Newsgroups: comp.unix.questions
Subject: Re: Problems with rm -f
Message-ID: <1991May14.214454.32197@mp.cs.niu.edu>
Date: 14 May 91 21:44:54 GMT
References: <1991May14.190816.17169@rodan.acs.syr.edu>
Distribution: usa
Organization: Northern Illinois University
Lines: 20

In article <1991May14.190816.17169@rodan.acs.syr.edu> jstewart@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@cs.niu.edu>
  Northern Illinois Univ.
  DeKalb, IL 60115                                   +1-815-753-6940