Mail Archives: djgpp/1996/03/26/02:10:26
Reply to message 8403959 from ELIZ AT IS DOT ELTA. on 03/25/96 11:58PM
>The best way to avoid grief is to not call programs which don't
>understand forward slashes. Don't use DEL, get a port of RM and use it
>instead.
Eww. :)
>I doubt that this can be easily fixed. But I'll look into this, as I now
>am working on making the DJGPP port of `find' better. An alternative
Mightn't it be possible to use alternative methods of sending the filenames
to -exec, similar to the -printf command? Something like an -execf, or a
modified syntax for the {} part? I agree that it wouldn't be easy, but it's
something to consider.
>would be to write a small program that knows about COMMAND.COM's internal
>commands which will convert the slashes, then call COMMAND with the fixed
>command line. You can then mention that program as the argument to -exec.
Another eww. Actually, that might be kinda fun to write. It wouldn't even
need to
know anything special though, would it? Just haveit invoke the command it is
passed, converting all forward slashes in the arguments to backslashes. Hmm...
I know there is a way to prevent a program from performing wildcard expansion
on
its arguments, but I forget what it is... (aside from enclosing said arguments
in
quotes, that is.)
>Btw, did you install the patches to `find' that I posted a month or so
>ago? Without that patch, you will see additional problems when you use
>-exec while recursively processing subdirectories.
Err... I think I deleted that message. Besides, I'd really rather not have to
download and recompile the source for find. Is there a binary patch available,
or better yet, a fresh version for download?
>> As a separate question, has anybody ported xargs to DJGPP yet?
>I have an almost finished port, but I can't resume working on it before
>the next week.
That's ok. I just wanted to know if it was going to be available or not.
Thanks a lot for the help!
John
- Raw text -