Mike Frysinger <[EMAIL PROTECTED]> wrote:
> $ foo="a b c"
> $ gawk 'BEGIN {foo="'${foo}'"}'
> gawk: BEGIN {foo="a
> gawk:^ unterminated string
This is normal. man bash:
# Word Splitting
# The shell scans the results of parameter expansion, command substitu-
# tion, an
On Wednesday 03 May 2006 21:42, Mike Frysinger wrote:
> the proposed hack:
> http://lists.gnu.org/archive/html/bug-bash/2006-03/msg5.html
>
> seems to work for this test case ...
but then seems to break another one:
export LC_ALL=C
PS1='\[\e[0;33m\]\u\[\e[0m\] '
printf a > foo.txt
cat foo.txt
ignoring the fact that i can pass in variables to gawk using the '-v' option,
i'm wondering if this is a bug in how bash expands variables to pass to
programs ... i couldnt pick out anything under EXPANSION, but that's probably
just because i missed it ;)
take for example:
$ foo="a b c"
$ gawk
Have just read the archives... ;) Forwarding to the list accordingly!
-- Forwarded Message --
Subject: Re: Bash-3.1.17 gets lost looking for end of string in certain
contexts
Date: Wednesday 03 May 2006 22:36
From: Richard <[EMAIL PROTECTED]>
To: Eric Blake <[EMAIL PROT
to dig up this thread yet again :)
http://lists.gnu.org/archive/html/bug-bash/2006-03/msg6.html
a user reported this with bash-3.0.17 with a good test case:
http://bugs.gentoo.org/130955
and i'm able to reproduce this here by setting my PS1:
PS1='$(echo "Strange \[\e[0;32m\]Prompt\[\e[0m\] ")
