From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-10704-mason-zsh=primenet.com.au@sunsite.auc.dk>
Received: (qmail 990 invoked from network); 12 Apr 2000 15:06:50 -0000
Received: from sunsite.auc.dk (130.225.51.30)
  by ns1.primenet.com.au with SMTP; 12 Apr 2000 15:06:50 -0000
Received: (qmail 13311 invoked by alias); 12 Apr 2000 15:06:40 -0000
Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm
Precedence: bulk
X-No-Archive: yes
X-Seq: 10704
Received: (qmail 13299 invoked from network); 12 Apr 2000 15:06:40 -0000
X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer goliath.siemens.de)
From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Bart Schaefer" <schaefer@candle.brasslantern.com>,
   "Zsh hackers list" <zsh-workers@sunsite.auc.dk>,
   "Sven Wischnowsky" <wischnow@informatik.hu-berlin.de>
Subject: RE: Should we backup this change? RE: Modifier substitutions.
Date: Wed, 12 Apr 2000 19:06:35 +0400
Message-ID: <000601bfa490$b188ed50$21c9ca95@mow.siemens.ru>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-reply-to: <1000412145336.ZM12301@candle.brasslantern.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700

>
> The change went in in 6002.  It was followed in 6003 by a
> change to allow
> a leading double backslash to escape the delimiter.  So all
> you need to
> do is change uses of ${foo/$bar/...} into ${foo/\\$bar/...}
> to avoid the
> confusion.  And without 6002, there's no way to build up an anchored
> pattern in a variable (which was Andrej's original complaint).
>

The problem is (as I discovered later) it is not complete. There is no
way to anchor pattern to match full string. And my original problem is
better solved with back-references anyway (that were not available at
the time of my question).

-andrej