- Original Message -
From: "Chet Ramey" <[EMAIL PROTECTED]>
To: "Stahlman Family" <[EMAIL PROTECTED]>
Cc: ; <[EMAIL PROTECTED]>
Sent: Friday, January 26, 2007 5:36 PM
Subject: Re: Unexpected behavior observed when using [EMAIL
PROTECTED]/patter
Stahlman Family wrote:
> The result of all this is that for the "+", "-", and "=" parameter
> expansion
> constructs, nested double-quote pairs in the rhs are stripped, but for
> patsub
> constructs they are not. Is this difference by design?
Yes. The patsub construct is implemented as in ksh93.
> Note that the goal in the examples below is to prepend "-iname '" (portion
> within double quotes only) to each of the 2 elements in the original array,
> without changing the number of words. i.e., the new array should contain the
> following 2 words:
> -iname 'abc
> -iname 'def
Thanks for
> > Note that the goal in the examples below is to prepend "-iname '" (portion
> > within double quotes only) to each of the 2 elements in the original array,
> > without changing the number of words. i.e., the new array should contain the
> > following 2 words:
> > -iname 'abc
> > -iname 'def
Tha
- Original Message -
From: "Stahlman Family" <[EMAIL PROTECTED]>
To:
Sent: Sunday, December 31, 2006 4:18 PM
Subject: Unexpected behavior observed when using [EMAIL
PROTECTED]/pattern/string} construct
While writing a script that uses the [EMAIL PROTECTED
While writing a script that uses the [EMAIL PROTECTED]/pattern/string}
construct,
I encountered behaviors I cannot reconcile with the text in the bash manual.
I've pasted snippets from a command line session below (with comments
interspersed) that shows the apparent issues.
Perhaps some of the c
