Message-ID: <3058f9b40707101411r3e2b5b07t5419ec901d83e805@mail.gmail.com>
Date: Tue, 10 Jul 2007 23:11:04 +0200
From: "Ariel Burbaickij" <ariel.burbaickij@gmail.com>
To: cygwin@cygwin.com
Subject: find(1) behaving strange or do I miss something
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Hello all,
following situation:
I hate white spaces in file and cranked tiny bashscript for replacing
them that goes like this:
for i in `find . -type f`
do
mv $i /some_directory/`echo $i|sed 's/ /_/g'`
done

On this I get complaints from mv that it cannot find files that are
basically parts of the
name with spaces like this:

idiotic file with whitespaces

cannot stat 'idiotic' -- no such file or directory
cannot stat 'file' -- no such file or directory

Truth to be told I hoped that find would still manage to treat them as
single entity.
Are my expectations to high or is it bug indeed?

/wbr
Ariel Burbaickij

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/