On 29/01/06, Norberto Bensa [EMAIL PROTECTED] wrote:
Perhaps you got some file named: hey I am a long file name with spaces.jpg ;)
No it can't be that, see the for before hand, that will separate at
whitespace by default (unless you tamper with IFS), so the variable
tested will be without
znx wrote:
No it can't be that, see the for before hand, that will separate at
whitespace by default
No, it won't. Try it.
(unless you tamper with IFS), so the variable
tested will be without whitespace,
No, it won't.
I can only guess its a charset or
similar that is causing the issue.
First off.. OH!
On 30/01/06, Alexander Skwar [EMAIL PROTECTED] wrote:
znx wrote: No it can't be that, see the for before hand, that will separate at whitespace by defaultNo, it won't. Try it.
True, ok so it did? and not now with bash3, I presume this is why it worked before and doesn't now?
On Sun, 2006-01-29 at 18:05 +, znx wrote:
Hi,
for x in *.JPG; do
if [ ! -e current/$x ]; then
I can't see anything wrong with this in particular, one thing that
springs to mind is to quote the string that you are testing:
for x in *.JPG; do
if [ ! -e
Michael Sullivan wrote:
for x in *.JPG; do
if [ ! -e current/$x ]; then
Hope that helps
Yep, that worked! Thanks! Hmm, I wonder why it worked before?
Perhaps you got some file named: hey I am a long file name with spaces.jpg ;)
--
Norberto Bensa
Ciudad de Buenos Aires, Argentina
5 matches
Mail list logo
