On Sat, Apr 12, 2008 at 9:52 AM, Stuart Jansen <[EMAIL PROTECTED]> wrote: > Specifically, Bash is leaking the output > of find to the screen and horking stdin.
Erm, what, exactly is leaking to the screen? How is stdin getting horked? Do some of your filenames have spaces or other characters which clash with the shell's reader? I don't know if this is applicable to your problem, but find -print0 | xargs -0 is often much less troublesome than find|while read. For example: find . -name '*.txt' -print0 | xargs -0 -n 1 aspell -c Chris /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
