| 1 |
First off.. OH! |
| 2 |
|
| 3 |
On 30/01/06, Alexander Skwar <listen@×××××××××××××××.name> wrote: |
| 4 |
> |
| 5 |
> znx wrote: |
| 6 |
> |
| 7 |
> > No it can't be that, see the "for" before hand, that will separate at |
| 8 |
> > whitespace by default |
| 9 |
> |
| 10 |
> No, it won't. Try it. |
| 11 |
|
| 12 |
|
| 13 |
True, ok so it did? and not now with bash3, I presume this is why it |
| 14 |
"worked" before and doesn't now? |
| 15 |
|
| 16 |
> (unless you tamper with IFS), so the variable |
| 17 |
> > tested will be without whitespace, |
| 18 |
> |
| 19 |
> No, it won't. |
| 20 |
|
| 21 |
|
| 22 |
See above! |
| 23 |
|
| 24 |
> I can only guess its a charset or |
| 25 |
> > similar that is causing the issue. |
| 26 |
> |
| 27 |
> I rather suppose, that he has filenames with spaces. |
| 28 |
|
| 29 |
|
| 30 |
Absolutely! |
| 31 |
|
| 32 |
> Anyway, good to see that it sorted it, point for the future, quote your |
| 33 |
> > variables in [ ] 's :) |
| 34 |
> |
| 35 |
> Of course - ever and always quote variables, unless you can be |
| 36 |
> totally certain about the contents. |
| 37 |
|
| 38 |
|
| 39 |
:P |
| 40 |
|
| 41 |
Alexander Skwar |
| 42 |
|
| 43 |
|
| 44 |
My apologies Alexander, I shall move my head into a bucket now for around 4 |
| 45 |
days. |
| 46 |
|
| 47 |
Thanks |
Archives