After trying a lot of different things (in order to get the output to load a [text]), I discovered if I slow down the output it works fine.

I hope this may help you, if you may ever need to do such a thing.

Sincerely,
S

FAILS: ls -1 ~/pd-externals/tof/*
WORKS: find ~/pd-externals/tof -exec sleep 0.001 ; -print

@svanya I recall an object called [pipe] - not sure if it would help. That's a bit strange.

@EEight
Cool! Found it. (5.reference). I will see if that helps. And post back here.
Thanks.

@svanya I don't get cut output, but I do get some lines broken into two at odd places like the middle of a word, or is that what you meant? It looks to happen with any program that dumps large amount of data at once, ls > file && cat file produces breaks in the same places as just ls, perhaps {shell} stores output in a variable or something that has a limited size and it just dumps the output anytime that limit is hit.

As a side note, it looks like [shell] runs commands in the users default shell and this can not be changed, so portability could easily become a problem, best to stick to POSIX commands if you plan on sharing the patch.

@oid
Thanks for the tip about Posix

Having trouble figuring this out though: Does POSIX support the following by default: grep, find, readlink?

Thanks, in advance. Much appreciated.

Neither are POSIX, readlink will work on most things *nix/bsd and fail on most (if not all) OSX (unless it was installed third party) and all Windows, grep can be considered safe for all *nix/bsd and OSX but will fail on most all Windows. I assume find will also fail on Windows, but I have no real idea. Using [shell] can be tricky if you want it to work on everything, many systems are not fully POSIX complient. Best to stick to sh commands and basic utilities if you go down that path, which will do most everything, just may take an extra step or two.

I am somewhat guessing on those failing on Windows, suspect it is correct, but I have little experience.

@oid
I figured it out. You just make a requirement as to how deep the files are, ex. ./samples/maker/kit/*.wav.
Then you do:

Thank you, for your input.
-Peace

Even better...
To do recursion is:

[makefilename %s/**/*/*.wav]