From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Bart Schaefer" <schaefer@candle.brasslantern.com>,
"Zsh hackers list" <zsh-workers@sunsite.auc.dk>
Subject: RE: Extended glob patterns in ${...#..} RE: Un-patch: new pattern matching code
Date: Mon, 9 Aug 1999 10:25:15 +0400 [thread overview]
Message-ID: <000901bee22f$f13b05b0$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <990809042534.ZM25662@candle.brasslantern.com>
> Since a closure can match the empty string, the shortest matched portion
> is nothing. However, asking for the longest match definitely doesn't work:
>
> zagzig<9> print ${(SM)foo##*}
> ab12xy
> zagzig<10> print ${(SM)foo##([[:digit:]])#}
>
> zagzig<11>
>
Believe it or not, it does work today. I have no idea, what went wrong yesterday
(I thought, it was the problem of flag order ...):
bor@itsrm2:~%> foo=ab12xy
bor@itsrm2:~%> print ${(SM)foo##[[:digit:]]#}
12
bor@itsrm2:~%> print ${(MS)foo##[[:digit:]]#}
12
But still, this one is probably unexpected:
bor@itsrm2:~%> print ${(MSI:1:)foo##[[:digit:]]#}
12
bor@itsrm2:~%> print ${(MSI:2:)foo##[[:digit:]]#}
2
bor@itsrm2:~%> print ${(MSI:3:)foo##[[:digit:]]#}
The first is O.K. ... and the third is O.K., but the second? I believe, this is
a clear bug. The ``S'' flag must consider only non-overlapped matches (the same
way, sed works).
/andrej
next prev parent reply other threads:[~1999-08-09 6:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-06 15:47 Peter Stephenson
1999-08-07 9:02 ` Andrej Borsenkow
1999-08-07 17:48 ` Bart Schaefer
1999-08-08 10:04 ` Extended glob patterns in ${...#..} " Andrej Borsenkow
1999-08-09 4:25 ` Bart Schaefer
1999-08-09 6:25 ` Andrej Borsenkow [this message]
1999-08-09 17:10 ` Bart Schaefer
1999-08-09 8:21 ` Andrej Borsenkow
1999-08-09 17:23 ` Bart Schaefer
1999-08-09 8:10 ` Bug? " 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='000901bee22f$f13b05b0$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=schaefer@candle.brasslantern.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).