array matching: inconsistent behaviour ?

array matching: inconsistent behaviour ?

[rahul]

[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]

Or am I doing the matching wrong? I am storing file names in an array.
Later I match filenames against those in the array for various purposes.
The filenames contain spaces and in this unfortunate case round brackets.
File names with brackets are failing the match.

FOO=()
x="a file"
y="a(file)b"

FOO+=($x)
FOO+=($y)

print $FOO[(i)$x]
print $FOO[(i)$y]

#  Now I found, that if i quote the string while matching then the comma
file matches, but now the space file fails.

print $FOO[(i)$x:q]
print $FOO[(i)$y:q]

If I escape/quote the string when adding to the array then again one of the
two matches fails. In any case, I cannot escape the names when inserting
into the array, as often double quoting/escaping happens when methods are
called repeatedly, and external commands give errors if they get quoted
filenames. I only quote the string finally if I am "eval"ing a command.

I'd like to know if I am doing this wrong, is there a consistent way of
matching the string inside the array.
-- 
 rahul

Re: array matching: inconsistent behaviour ?

[Han Pingtian]

On Wed, Jan 09, 2013 at 12:00:34PM +0530, rahul wrote:
> Or am I doing the matching wrong? I am storing file names in an array.
> Later I match filenames against those in the array for various purposes.
> The filenames contain spaces and in this unfortunate case round brackets.
> File names with brackets are failing the match.
> 
> FOO=()
> x="a file"
> y="a(file)b"
> 
> FOO+=($x)
> FOO+=($y)
> 
> print $FOO[(i)$x]
> print $FOO[(i)$y]
> 
Looks like if using "e" flag, both would be matched here.

Re: array matching: inconsistent behaviour ?

[rahul]

[-- Attachment #1: Type: text/plain, Size: 330 bytes --]

On Wed, Jan 9, 2013 at 3:05 PM, Han Pingtian <hanpt@linux.vnet.ibm.com>wrote:

> Looks like if using "e" flag, both would be matched here.
>

Yes, (ie) works perfectly. Found it in the document:

    |  This flag causes any pattern matching that would be performed on the
subscript to use plain string matching instead
-- 
 rahul

Re: array matching: inconsistent behaviour ?

[Peter Stephenson]

On Wed, 09 Jan 2013 12:00:34 +0530
rahul <rahul2012@gmail.com> wrote:
> Or am I doing the matching wrong? I am storing file names in an array.
> Later I match filenames against those in the array for various
> purposes. The filenames contain spaces and in this unfortunate case
> round brackets. File names with brackets are failing the match.
> 
> FOO=()
> x="a file"
> y="a(file)b"
> 
> FOO+=($x)
> FOO+=($y)
> 
> print $FOO[(i)$x]
> print $FOO[(i)$y]
> 
> #  Now I found, that if i quote the string while matching then the
> comma file matches, but now the space file fails.
> 
> print $FOO[(i)$x:q]
> print $FOO[(i)$y:q]

You're not exactly doing anything wrong, but quoting here has alwas been
a bit funny to allow (some forms of) pattern matching.  To ensure an
exact string match you can use the (e) flag...

% print $FOO[(ie)$x]
1
% print $FOO[(ie)$y]
2

pws

Re: array matching: inconsistent behaviour ?

[rahul]

[-- Attachment #1: Type: text/plain, Size: 1196 bytes --]

On Wed, Jan 9, 2013 at 3:10 PM, Peter Stephenson

> You're not exactly doing anything wrong, but quoting here has alwas been
> a bit funny to allow (some forms of) pattern matching.  To ensure an
> exact string match you can use the (e) flag...
>
> % print $FOO[(ie)$x]
> 1
> % print $FOO[(ie)$y]
> 2
>
> pws
>

My apologies. There's just so much zsh provides, it's difficult for a
newcomer to keep it all in the head even though I have printouts next to
me. You've done an awesome job with zsh!

I've been using the "print -rC" to print in columns -- saves me from quite
a bit of programming. However, often the data has spaces in it, or tabs. Of
course, print will wrap/break on those. So i found a hack to use "tr" to
replace spaces and tabs with ^a and ^b before feeding to "print" and then
doing the reverse after "print" gives the output. However, putting the
spaces back after "print" has done its formatting means that the alignment
is disturbed by the spaces.

I tried to change the IFS to newlines before calling print, but it seems
"print" does not use IFS to wrap/split lines into columns. Is there some
direct way to prevent "print -rC" from wrapping on spaces and tabs.

-- 
 rahul

Re: array matching: inconsistent behaviour ?

[Bart Schaefer]

On Jan 9,  4:03pm, rahul wrote:
}
} I've been using the "print -rC" to print in columns -- saves me from quite
} a bit of programming. However, often the data has spaces in it, or tabs. Of
} course, print will wrap/break on those.

"print" doesn't do any wrapping/wordsplitting internally, so if you are
getting columns broken up on whitespace in the data, it's because of
command-line parsing.  Change the way you quote the arguments to print.

Re: array matching: inconsistent behaviour ?

[rahul]

[-- Attachment #1: Type: text/plain, Size: 729 bytes --]

On Wed, Jan 9, 2013 at 9:26 PM, Bart Schaefer <schaefer@brasslantern.com>wrote:

> On Jan 9,  4:03pm, rahul wrote:
> }
> } I've been using the "print -rC" to print in columns -- saves me from
> quite
> } a bit of programming. However, often the data has spaces in it, or tabs.
> Of
> } course, print will wrap/break on those.
>
> "print" doesn't do any wrapping/wordsplitting internally, so if you are
> getting columns broken up on whitespace in the data, it's because of
> command-line parsing.  Change the way you quote the arguments to print.
>

Okay, great- I just tried out a one-liner and it works:

    print -rC2 -- "${(@f)$(brew list --versions)}"

    print -rC2 -- "${(@f)$(print -rl -- *(.) | nl)}"

-- 
thx,  rahul