Re: How to handle whitespace in filenames ???

["Michael D. Schleif" <mds@helices.org>]

Mike Kuhar wrote:
> 
> How about:
> 
> find /etc -name pump\* -print
> 
> The \* supplies the wild card pump to find.  So any instance of pump and what
> follows is listed.  To find the instance of the file 'pump it' in /etc of any of
> it sub-directories.
> 
> find /etc -name pump\* -print | grep 'pump it'


Please, re-read my example, again ;>

You are grepping filenames -- I am grepping inside the named files . . .


> -----Original Message-----
> From: Michael D. Schleif [mailto:mds@helices.org]
> Sent: Wednesday, December 19, 2001 1:58 PM
> To: debian-user@lists.debian.org
> Cc: Debian Users List Service
> Subject: Re: How to handle whitespace in filenames ???
> 
> Ken Irving wrote:
> >
> > On Wed, Dec 19, 2001 at 12:26:05PM -0600, Michael D. Schleif wrote:
> > >
> > > More and more, *nix developers are following the dark path of using
> > > whitespace in directory and filenames -- something which I've always
> > > detested, from an sa standpoint ;<
> > >
> > > For example, on my upgraded potato box I may want to do something this
> > > simple:
> > >
> > >       grep pump `find /etc/ -type f`
> > >
> > > ...
> > >
> > > How do others handle this?
> >
> > The -exec option under find should't care what the name looks like:
> >
> >     $ find /etc/ -type f -exec -H pump {} \;
> 
> Of course, you meant this:
> 
>         find /etc/ -type f -exec grep -H pump {} \;
> 
> OK, this is workable in my example find/grep example.  I'll have to
> think on this for the general case.

-- 

Best Regards,

mds
mds resource
888.250.3987

Dare to fix things before they break . . .

Our capacity for understanding is inversely proportional to how much we
think we know.  The more I know, the more I know I don't know . . .