Path: utzoo!mnetor!tmsoft!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!samsung!spool.mu.edu!sol.ctr.columbia.edu!ira.uka.de!fauern!NewsServ!rommel
From: rommel@Informatik.TU-Muenchen.DE (Kai-Uwe Rommel)
Newsgroups: comp.os.os2.misc
Subject: Re: Question with forall
Keywords: forall
Message-ID: <1991Feb7.102301.1622@newsserv.informatik.tu-muenchen.de>
Date: 7 Feb 91 10:23:01 GMT
References: <23102@ttidca.TTI.COM>
Sender: news@newsserv.informatik.tu-muenchen.de
Organization: Technische Universitaet Muenchen, Germany
Lines: 28
Nntp-Posting-Host: dssiegert4.informatik.tu-muenchen.de

In article <23102@ttidca.TTI.COM> terence@ttidca.TTI.COM (Terence Davis) writes:
>select each file, pass it through sed (a port by Kai) to make the changes
>and rewrite the file with the same name.  Unfortunately, the files had no
>extension.  I tried
>	forall -R *
>	forall -R *.
>	forall -R *.[]
>and some others but none worked.  The -R is recursive down subdirectories.
>Each variation gave me either no files or all the files in each directory.

FORALL uses a PD file name matching routine which closely resembles the
Unix cmd line expandsion done by sh etc (with the extension of
{x,y,..}). With the Unix filename expansion, there is no way to specify
a pattern which matches all files that do NOT contain any dot but no
other file, this would require true regular expressions.

I consider to add regexp. to this program or at least add a -v switch
like grep has to cause FORALL to work on those files NOT matching the
pattern(s) which would allow you to use "FORALL -v *.* : ..." to work
on all files not containing a dot in their name.

(Unfortunately, the PD filename matching routine had a bug which caused
to fail [^abc] etc, i.e. inverted character groups. I will fix this too.)

If there is interest, I could then submit this new version to
comp.binaries.os2 when I finished it.

Kai Uwe Rommel