Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Bug in case stmt with '('
- X-seq: zsh-workers 1754
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxxx (Z Shell workers mailing list)
- Subject: Re: Bug in case stmt with '('
- Date: Wed, 24 Jul 1996 04:10:29 -0700
- In-reply-to: Zefram <A.Main@xxxxxxxxxxxxxxxxx> "Re: Bug in case stmt with '('" (Jul 24, 9:29am)
- References: <13422.199607240829@xxxxxxxxxxxxxxxxxxxxxxx>
- Reply-to: schaefer@xxxxxxx
On Jul 24, 9:29am, Zefram wrote:
} Subject: Re: Bug in case stmt with '('
}
} >I can't find any case where zsh doesn't permit '(' to be a glob metachar.
} >SH_GLOB relates to parameter and command substitutions, not filenames.
}
} Which is a failing, in my opinion. The glob syntax should be as
} consistent as possible (we seem to *need* some special handling in
} `case`). SH_GLOB having an effect only in certain places seems very
} silly, and is rather confusing. What's the rationale for it?
I confess to not understanding what it even *means* to "[disable] the
special meaning of `(', `|', `)' and `<' for globbing the result of
parameter and command substitutions." And what *are* the "some other
places where the shell accepts patterns" where this has effect?
One of them seems to be any command that takes a -m option as with
`typeset -m x\*' -- which seems bizarre to me; another is parameter
assignments with globsubst set. Others?
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.nbn.com/people/lantern
New male in /home/schaefer:
>N 2 Justin William Schaefer Sat May 11 03:43 53/4040 "Happy Birthday"
Messages sorted by:
Reverse Date,
Date,
Thread,
Author