Quote:
Originally Posted by
methyl
I cannot believe that I am the only person to have encountered problems with unix commands dealing with space characters in filenames.
Unix commands generally do not have problems with space characters in file names. The main exceptions are the commands that both parse their input and expand meta-characters in it. That includes mainly shell interpreters. So yes, there are a lot of issues with shell scripts and space characters in filenames. One way to overcome them has always been to use find and {}.
Quote:
The question still remains: Why have I seen the "{}" problem before?
The only reasonable explanation is you have been fooled by something else, didn't double check and stayed with that believing.
Quote:
I am exploring Reborg's ideas which imply that some older shells were eating the {}. If proven, this would explain it.
Older shells were all based on the original Bourne shell. Then came the C-shell, the Korn shell and later their open source clones and more or less innovative variants. I never heard of any of them handling {} a specific way.
Quote:
I don't have access to the source code to the various editions of "find" - unlike when I was working on enhancements to RSX.
As I wrote a couple of time, the find command itself has nothing to do with it as it does receive the very same parameter whether you quote {} or not.