bash limits ?
Chris F.A. Johnson
c.f.a.johnson-bJEeYj9oJeDQT0dZR+AlfA at public.gmane.org
Fri Sep 10 19:58:05 UTC 2004
On Fri, 10 Sep 2004, Peter L. Peres wrote:
>
> On Thu, 9 Sep 2004, Chris F.A. Johnson wrote:
>
>> On Thu, 9 Sep 2004, Peter L. Peres wrote:
>>>
>>> The exact command I'm using is:
>>>
>>> SORTED=$(find $TMPDIR/* -type f|grep -E [0-9]+|cut -d'/' -f4|sort)
>>
>> What error message is it giving you?
>
> Maybe I did not make myself clear: I do not get an error, some filenames
> simply get eaten is $SORTED is long enough. They are in $SORTED (I checked)
> but after I submit $SORTED to for ... they are gone. I will have to check
> again. Maybe I'm just wasting time and should go directly for a Perl
> solution.
Maybe you should post the exact code that is causing the
problem. The problem is not with "for".
Do you get different results with:
for file in $SORTED
do
printf "%s\n" "$file"
done
And:
printf "%s\n" $SORTED
If so, what are the differences?
--
Chris F.A. Johnson http://cfaj.freeshell.org
=================================================================
Everything in moderation -- including moderation
--
The Toronto Linux Users Group. Meetings: http://tlug.ss.org
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml
More information about the Legacy
mailing list