Subject: Re: This has GOT to be a bug in ksh...
To: None <netbsd-users@netbsd.org>
From: Daniel Mercer <dmercer@fantoccini.com>
List: netbsd-users
Date: 06/17/2002 10:49:12
Wow. Clearly, I should never hit 'send' before coffee.
I missed the fact that quotes were wanted around the filename. In
fact, the suggestion I was commenting on would not provide that
output either. Perhaps this is closer:
find . -type f | (while read f; do echo "\"$f\""; done)
"./Berra =E4ter ost"
"./Lisa visar rattarna"
I'm going to go hunt down that coffee now. =3D)
D
On Monday, June 17, 2002, at 10:38 AM, Daniel Mercer wrote:
> Hi folks,
>
>
> Maybe I'm missing something...
>
>>>> $ touch "Berra =E4ter ost" "Lisa visar rattarna"
>>>> $ for f in `find . -type f | sed -e 's/\(.*\)/"\1"/'` ; do echo $f =
;=20
>>>> done
>>>> "./Berra
>>>> =E4ter
>>>> ost"
>>>> "./Lisa
>>>> visar
>>>> rattarna"
>>>> $
>
> Okay...
>
>>> Oh yeah, I've run into this before. I never found a fix but here is =
a
>>> slow workaround.
>>>
>>> find . -type f | (while read f; do echo "$f"; done)
>
> Why won't:
>
> find . -type f| cat
>
> work?
>
> It seems to provide the same results as reading from stdin
> and echoing to stdout.
>
> Clearly, I'm missing something. =3D)
>
> Dan M.