Re: Unexpected behavior observed when using [EMAIL PROTECTED]/pattern/string} construct

2007-01-29 Thread Stahlman Family
- 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

Re: Unexpected behavior observed when using [EMAIL PROTECTED]/pattern/string} construct

2007-01-20 Thread Stahlman Family
> 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

Bugs pertaining to pathname expansion and field splitting (when IFS is null), caused by use of literal space to separate words generated by "dollar at" expansions

2007-01-15 Thread Stahlman Family
This post is essentially a follow-up to a previous post, initially made just before New Year's, which appears to have been overlooked. After making the original post, I delved into the bash source to determine why I was seeing the behavior described, and what I found convinced me that the behavior

Re: Unexpected behavior observed when using [EMAIL PROTECTED]/pattern/string} construct

2007-01-06 Thread Stahlman Family
- 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

Unexpected behavior observed when using [EMAIL PROTECTED]/pattern/string} construct

2006-12-31 Thread Stahlman Family
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

Re: Trailing null fields are discarded while leading ones are preserved

2006-12-21 Thread Stahlman Family
- Original Message - From: "Chet Ramey" <[EMAIL PROTECTED]> To: "Stahlman Family" <[EMAIL PROTECTED]> Cc: ; <[EMAIL PROTECTED]> Sent: Wednesday, December 20, 2006 7:26 AM Subject: Re: Trailing null fields are discarded while leading ones are prese

Re: Trailing null fields are discarded while leading ones are preserved

2006-12-20 Thread Stahlman Family
- Original Message - From: "Chet Ramey" <[EMAIL PROTECTED]> To: "Stahlman Family" <[EMAIL PROTECTED]> Cc: ; <[EMAIL PROTECTED]> Sent: Tuesday, December 19, 2006 9:00 AM Subject: Re: Trailing null fields are discarded while leading ones are preserv

Trailing null fields are discarded while leading ones are preserved

2006-12-18 Thread Stahlman Family
Although the section on word splitting in the Bash manual makes no distinction between leading and trailing null fields, Bash's word splitting algorithm will not preserve a trailing null field. The reason for this appears to be the following logic in list_string (much omitted): for (result = (W

Re: Despite text in gnu bash manual, quote removal appears to be performed on case pattern

2006-12-13 Thread Stahlman Family
- Original Message - From: "Chet Ramey" <[EMAIL PROTECTED]> To: "Stahlman Family" <[EMAIL PROTECTED]> Cc: ; <[EMAIL PROTECTED]> Sent: Tuesday, December 12, 2006 2:01 PM Subject: Re: Despite text in gnu bash manual, quote removal appears to be