Quote:
Originally Posted by
agama
Did you notice that there is a missing double quote on the last echo in the script? I would have expected you to have seen an error, but the behaviour might be exactly as you described all caused by the missing quote.
Spot on, agama. I ran it with the fixed (?!) variables and such on a much smaller folder of files than I was "playing it on" before, and first thing to come up was "syntax error -- unexpected end of file." I cat'ed and immediately saw the missing double-quote.
Never let it be said that coloured syntax formatting in a GUI text editor is an unqualified benefit -- sometimes the eye is so enwrapt in the colours that the mind is rendered blind to the errors staring one straight in the face!
Quote:
Originally Posted by agama
I don't know why it wouldn't toss an error to stderr, but if it isn't, or stderr is being redirected (I don't think you are), then it would appear not to be executing the commands after the done.
My bad there. I had stderr going out to /dev/null, anticipating that the only errors I'd have seen in stdout would have been related to the files "punch branded" by PhotoFiltre or some other maker-related error. I didn't see the eof error for that reason. It's not like BASH exactly allows one to pick and choose which kind, app error or shell syntax error, one gets to redirect (or is it? I certainly haven't seen any how-to's on this score). And even the author, Andreas Huggel, says error trapping in his app needs some looking at -- presently all you get is what the error/s is/are, not what file tossed them up. It's a matter of "feeding protein" to the -V option or a more file-conscientious rewrite of the whole error-reporting section of the code. No news yet as to whether Hr Huggel has made headway.
I made the fix, and tried again. It ran beautifully. Now, paradoxically, I'm thinking a better "cure" for PhotoFiltre EXIF software "branding" tags might not be to purge them, but to erase and rewrite them in the way that won't habitually create an error call in Exiv2. Ideally such a script would sync with a query at the top (return value of same stored in a variable) to the
registry asking for the exact version number of PF right down to the build string. But that's a whole other lunch date,.
Thanks again for the help.
BZT