Shell Programming and Scripting

See man find for your system (whatever that is?). If it is not there, just use \; as usual. The + can be faster on certain Operating System (e.g. modern Solaris).

Apache is a package which you can install on unix of Linux. Whether it be unix of Linux, the Operating System will support space characters in filenames.

The sentence supplement containing "MD5" makes no sense whatsoever to me.

"Escape Sequences" are usually associated with driving special effects on Printers and VDUs. What do you mean?

Please provide examples of awkward directory names which you wish to exclude (blotting anything confidential with X's).
When the list gets awkward the best approach is to use sed with a sedfile to eliminate unwanted file or directory names. Using a sedfile means that the Shell does not see the awkward names and therefore cannot confuse the situation.

Sorry that was my very first post.
Every single option when referring to options on a long command??? It wasn't code... it was a diagnostic message issued by awk copied and pasted from the terminal window. Some of the things marked above are
awk options not a complete statement. Are you saying you want every tiny fragment put in CODE tags as was done above?
I wasn't aware it was doing that, I was pasting from a plain text editor.
I don't know how to determine the version of Linux, (find (GNU findutils) 4.4.2) but neither are obscure, (although I agree the options could be considered obscure) they are from a very current version of CentOS, which is being run by a major web hosting company (AFAIK many of the major shared hosts use this OS).

---------- Post updated at 11:36 AM ---------- Previous update was at 10:40 AM ----------

Thanks for this - I saw this \; sequence on the original code that I got the statement from, but it was using \ to break the statement up into multiple lines. I thought \; was a an artifact left over from editing (having the meaning of "null/empty line"). I couldn't find \; in the man pages - I went back and checked again and found + which appears to be the preferred syntax. Find is very powerful, but I find it very hard to grok - been programming for 35 years, but very new to shell scripting. I don't do enough bash scripting to keep sharp with the syntax, so I have to look almost everything up as I go so I really appreciate when the gurus here can look at a statement and give a quick pointer or hint.

Sorry maybe I should have said escaping?? i.e. preceeding with \ to ignore the special meaning of the next character or include a character like a blank or quote.

I am running this script in the home directory of a shared host. AFAIK whitespace is not allowed in URL's (filenames in public_html) I certainly don't use whitespace in these names. I'm also not expecting to see them in the files of open source packages like wordpress, drupal, etc. Is module with whitespace.class.php even legal? AFAIK it isn't, and my current belief is that no good programmer would do it.

Am I naive in these assumptions? I didn't expect to find these, so I didn't design the script with that in mind, but after your post I did a test and the line of code in question did work correctly even on a filename with a space in it.

The code tags thing is so everyone can see significant space characters in commands or messages. It is much easier to read a post if code is separated from comment. It is not necessary to put every code fragment in code tags but it can reduce ambiguty when the command is an English word (like "find").

I too do not like space characters in file names or URLs, though I believe that the are valid in both circumstances. When in an URL, a space character is represented by %20.