From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Peter Stephenson" <pws@cambridgesiliconradio.com>,
"Zsh hackers list" <zsh-workers@sunsite.auc.dk>
Subject: RE: Modifier substitutions.
Date: Thu, 6 Apr 2000 13:32:38 +0400 [thread overview]
Message-ID: <000e01bf9fab$0c3e59a0$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <0FSL00D608EDHX@la-la.cambridgesiliconradio.com>
>
> The `#' is being interpreted as an anchor at the head of the
> string even
> when buried inside $old. I have a feeling that wasn't my intention.
>
Erm ... it was done by Bart (do not have arcticle number handy) as a
result of my question. It was originally used when _configure called
_long_options (was it called so?) to make "--disable-*" out of
"--enable-*" (and vice versa). It gets pattern/replacement in the form
'#--disable- --enable-'
...
The intent was to not match string in the middle of option (it is
unlikely in case of configure, but for the sake of generality ...) But,
probably, now, with backreferences it can be rewrited as
'(#m)--disable-(*) --enable-$MATCH'
and explicitly anchor at the beginning.
I do not insist on this change. This was the sole reason for it.
-andrej
next prev parent reply other threads:[~2000-04-06 9:33 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 [this message]
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
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='000e01bf9fab$0c3e59a0$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=pws@cambridgesiliconradio.com \
--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).