Configuration Information [Automatically generated, do not change]:
Machine: i386
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i386-redhat-linux-gnu'
-DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/share/locale'
-DPACKA
On Friday 18 April 2008 14:02, Dave Rutherford wrote:
> Quotes or escapes in the output of the `` are input to the shell rather
> than shell syntax, so won't be interpreted. You just need to quote more.
>
> $ foo () { echo sony; echo apple; echo hewlett packard; }
>
> Now note the difference be
On Friday 18 April 2008 14:02, Dave Rutherford wrote:
> Quotes or escapes in the output of the `` are input to the shell rather
> than shell syntax, so won't be interpreted. You just need to quote more.
>
> $ foo () { echo sony; echo apple; echo hewlett packard; }
>
> Now note the difference be
"Dave Rutherford" <[EMAIL PROTECTED]> writes:
> Now note the difference between:
>
> $ for w in "`foo`"; do echo $w; done
> sony apple hewlett packard
>and
> $ for w in `foo`; do echo "$w"; done
> sony
> apple
> hewlett
> packard
>and
> $ for w in "`foo`"; do echo "$w"; done
> sony
> apple
On Thu, Apr 17, 2008 at 4:21 PM, luiscolorado <[EMAIL PROTECTED]> wrote:
> Hello, everybody... I'm suffering a huge problem with the "for" command
> because it wants to parse a variable ignoring escape characters.
>
> For example, as you know, if I do something like this in bash:
>
> for i in s
OK, glad that it is fixed in bashes beyond what Debian sid uses.
M> you still didn't answer my question, which was "what version are you using"?
Did too:
>> 02:26 /$ echo $BASH_VERSION
>> 3.1.17(1)-release
Over and out.
