From: Peter Stephenson <pws@cambridgesiliconradio.com>
To: zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Re: Should we backup this change? RE: Modifier substitutions.
Date: Thu, 13 Apr 2000 09:59:37 +0100 [thread overview]
Message-ID: <0FSY00CA66BCLS@la-la.cambridgesiliconradio.com> (raw)
In-Reply-To: "Your message of Thu, 13 Apr 2000 10:00:05 +0400." <000001bfa50d$83d622b0$21c9ca95@mow.siemens.ru>
> BTW where are these (#s) and (#e) useful? The patterns in parameter
> expansions are anchored by definition; the patterns in conditional
> expressions/case statements are anchored to full word as well. Could you
> provide example where you cannot do without (#s)/(#b)?
In alternatives. Try reading the manual entry.
> In any case, this is additional argument in favour of backing out this
> change (assuming, that these (#s)/(#b) really work).
If they worked here it would certainly simplify substitutions; although
there are ways of doing most things with the existing anchors, they are
even less readable and memorable (and that's saying something).
--
Peter Stephenson <pws@cambridgesiliconradio.com>
Cambridge Silicon Radio, Unit 300, Science Park, Milton Road,
Cambridge, CB4 0XL, UK Tel: +44 (0)1223 392070
next prev parent reply other threads:[~2000-04-13 9:00 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
2000-04-12 20:54 ` Peter Stephenson
2000-04-13 6:00 ` Andrej Borsenkow
2000-04-13 8:59 ` Peter Stephenson [this message]
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=0FSY00CA66BCLS@la-la.cambridgesiliconradio.com \
--to=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).