bash limits ?

Lennart Sorensen lsorense-1wCw9BSqJbv44Nm34jS7GywD8/FfD2ys at public.gmane.org
Fri Sep 10 20:13:07 UTC 2004


On Fri, Sep 10, 2004 at 05:52:55PM -0400, Peter L. Peres wrote:
> 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.

Does any of the filenames contain spaces?  Your current solution would
die on spaces for sure.

> It should but it will get more complicated later, I will want to prune 
> certain filenames (intersect with a list and keep what is not in it). It 
> will probably be done in Perl later, I just tinker with the ideas for now. 
> I would like to know what's broken ?

Perl may be simpler to start with then.  Something like: find ... |
perl, with perl eating filenames from stdin one per line would probably
be better.

Lennart Sorensen
--
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