delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2000/05/18/01:46:29

From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: recursive rm
Date: 16 May 2000 07:52:20 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 26
Message-ID: <8fqunk$70u$1@nets3.rz.RWTH-Aachen.DE>
References: <8fpiqe$gpr$1 AT slb6 DOT atl DOT mindspring DOT net>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 958463540 7198 137.226.32.75 (16 May 2000 07:52:20 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 16 May 2000 07:52:20 GMT
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Dr. J. Robert Lee <jrl AT netcom DOT com> wrote:
> group work fine with the Unix "find" command, but
> not with DOS.
[...]
> These are the suggestions for Unix. DOS anyone?

> find . -name "*.o" -exec rm {} \;

That line *does* work with the DJGPP ports of GNU find and GNU
fileutils, almost verbatim. You just have to remove the '\' before the
';', maybe.  Actually, I'ld usually not use '-exec' for that, but

	find . -name "*.o" | xargs rm -v

It's faster by not calling up 'rm' that often, and the '-v' lets you see
what's happening.

OTOH, with DJGPP's enhanced globbing code built into the C runtime
library, it's usually simpler to just

	rm .../*.o

and be done with it. 
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019