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 [thread overview]
Message-ID: <000601bfa490$b188ed50$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <1000412145336.ZM12301@candle.brasslantern.com>
>
> 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
next prev parent reply other threads:[~2000-04-12 15:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-06 9:15 Peter Stephenson
2000-04-06 9:32 ` Andrej Borsenkow
2000-04-06 12:49 ` Andrej Borsenkow
2000-04-12 12:26 ` Should we backup this change? " Andrej Borsenkow
2000-04-12 12:34 ` Sven Wischnowsky
2000-04-12 14:53 ` Bart Schaefer
2000-04-12 15:06 ` Andrej Borsenkow [this message]
2000-04-12 20:54 ` Peter Stephenson
2000-04-13 6:00 ` Andrej Borsenkow
2000-04-13 8:59 ` Peter Stephenson
2000-05-04 7:02 ` Let's do it " Andrej Borsenkow
2000-05-04 15:56 ` Peter Stephenson
2000-05-05 13:32 ` PATCH:RE: Let's do it RE: Should we backup this change? RE: Modifiersubstitutions Andrej Borsenkow
2000-05-05 14:26 ` PATCH: substitution anchors Peter Stephenson
2000-05-05 14:52 ` Bart Schaefer
2000-05-05 14:55 ` Andrej Borsenkow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000601bfa490$b188ed50$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=schaefer@candle.brasslantern.com \
--cc=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).