On Thursday 04 May 2006 11:37, Paul Jarc wrote:
> Mike Frysinger <[EMAIL PROTECTED]> wrote:
> > On Thursday 04 May 2006 00:44, Paul Jarc wrote:
> >> What do you mean by "fail"? What do you want to happen in this case?
> >
> > i meant gawk hates it ... not bash
>
> Ok, and what about the second que
> Just curious: why is it that your version displays 6 within parenthesis,
whereas mine displays 2?
Shame on me. Decided to stop being lazy and get the answer from the
source: man bash... ;)
Curiosity satistied: please kindly disregard.
Richard
___
Mike Frysinger <[EMAIL PROTECTED]> wrote:
> On Thursday 04 May 2006 00:44, Paul Jarc wrote:
>> What do you mean by "fail"? What do you want to happen in this case?
>
> i meant gawk hates it ... not bash
Ok, and what about the second question? What are you trying to do
that you haven't figured ou
On Thursday 04 May 2006 11:08, Mike Stroyan wrote:
> A little more bash syntax can quote newlines for awk.
this is when you start using gawk -v foo="$foo" ...
i was using gawk as an example of my variable expansion question, not as a way
to figure out how to pass a variable into gawk
-mike
___
A little more bash syntax can quote newlines for awk.
$ foo="a
b
c"
$ lf="
"
$ gawk 'BEGIN {foo="'"${foo//$lf/\\n}"'"} END {print foo}' /dev/null
a
b
c
--
Mike Stroyan
[EMAIL PROTECTED]
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/
On Thursday 04 May 2006 00:44, Paul Jarc wrote:
> 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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Richard on 5/3/2006 7:50 PM:
> Just curious: why is it that your version displays 6 within parenthesis,
> whereas mine displays 2?
The number in parenthesis matches the number of times you have rebuilt in
your local tree (also encod
Richard <[EMAIL PROTECTED]> writes:
> Compiling grep-2.5.1a and during its tests, test #121 is not completed
> because of following error messages by bash:
>
> spencer1.script: line 602: unexpected EOF while looking for matching `''
> spencer1.script: line 608: syntax error: une
