From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-17210-mason-zsh=primenet.com.au@sunsite.dk>
Received: (qmail 6444 invoked from network); 23 May 2002 05:05:56 -0000
Received: from sunsite.dk (130.225.247.90)
  by ns1.primenet.com.au with SMTP; 23 May 2002 05:05:56 -0000
Received: (qmail 3634 invoked by alias); 23 May 2002 05:05:46 -0000
Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm
Precedence: bulk
X-No-Archive: yes
X-Seq: 17210
Received: (qmail 3620 invoked from network); 23 May 2002 05:05:45 -0000
Date: Wed, 22 May 2002 22:05:36 -0700 (PDT)
From: Bart Schaefer <schaefer@brasslantern.com>
Sender: schaefer@ns1.sodaware.com
To: JulioB <juliob@ugcs.caltech.edu>
cc: zsh-workers@sunsite.dk
Subject: Re: bug: ${a%>}
In-Reply-To: <200205230358.g4N3wDIh018379@beg.ugcs.caltech.edu>
Message-ID: <Pine.LNX.4.44.0205222142070.28780-100000@ns1.sodaware.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 22 May 2002, JulioB wrote:

> Is this a bug or have I been smoking the same shit as Dubya?

Possibly both.  configure with --enable-zsh-debug and:

schaefer<502> echo ${a#<} ${a%>} ${a#\<} ${a%\>}
Oops. Bug in parse_subst_string: len < l
text> <text> text> <text

The problem is actually with the parsing of LX2_OUTANG in gettokstr(),
but I don't immediately see how to fix it.