in reply to find2perl -exec on Windows

It looks broken to me.

You could post process the output by piping it through something like:

perl -p -e "s/^(File::Find::find)/my \$cwd = Cwd::cwd();$1/"

You might want to test that before you run it. And you don't have to tell me - it's ugly.

Replies are listed 'Best First'.
Re^2: find2perl -exec on Windows
by QM (Parson) on Feb 12, 2005 at 00:21 UTC
    perl -p -e "s/^(File::Find::find)/my \$cwd = Cwd::cwd();$1/"
    Thanks, that's a good suggestion.

    I'm trying to put something together for...how do you say...lusers, who aren't that sophisticated, and probably couldn't type that in given 10 tries. Ultimately I'm going to make a standalone that they can give options too, like:

    foo . -mtime -7 -ls
    Though now that I think about it, that might be too much for them also.

    I've now got a version of find2perl that works for -ls and -exec in windows (but is unchanged elsewhere). I've tried this in the find2perl output to reduce typing on the luser's part:

    open(STDOUT,'|perl') or die "...";
    but the command prompt returns before the final output starts and the first line of output doesn't line up. Reopening STDOUT and printing a newline seems to fix this.

    -QM
    --
    Quantum Mechanics: The dreams stuff is made of