From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from euclid.skiles.gatech.edu (list@euclid.skiles.gatech.edu [130.207.146.50]) by melb.werple.net.au (8.7.5/8.7.3/2) with ESMTP id SAA04729 for ; Wed, 24 Jul 1996 18:36:50 +1000 (EST) Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id EAA05808; Wed, 24 Jul 1996 04:30:25 -0400 (EDT) Resent-Date: Wed, 24 Jul 1996 04:30:25 -0400 (EDT) From: Zefram Message-Id: <13422.199607240829@stone.dcs.warwick.ac.uk> Subject: Re: Bug in case stmt with '(' To: zsh-workers@math.gatech.edu (Z Shell workers mailing list) Date: Wed, 24 Jul 1996 09:29:21 +0100 (BST) In-Reply-To: <960723145553.ZM3351@candle.brasslantern.com> from "Bart Schaefer" at Jul 23, 96 02:55:53 pm X-Loop: zefram@dcs.warwick.ac.uk X-Stardate: [-31]7856.76 X-US-Congress: Moronic fuckers MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"CeN6e.0.gQ1.WyTzn"@euclid> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/1751 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu >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? -zefram