From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: backreferences
Date: Thu, 15 Oct 2015 22:46:34 -0700 [thread overview]
Message-ID: <56208F3A.1040706@eastlink.ca> (raw)
In-Reply-To: <151015222827.ZM30858@torch.brasslantern.com>
On 10/15/2015 10:28 PM, Bart Schaefer wrote:
> On Oct 15, 10:05pm, Bart Schaefer wrote:
> }
> } However, (^foo)(*) could be very useful with backreferences, because
> } (^foo) puts everything up to "foo" into $match[1], and then (*) puts
> } from "foo" to the end into $match[2].
>
> And now I've got two problems instead of one.
>
> Because of course (^foo) matches "foobar" even though the latter has
> "foo" as a prefix. You need (^foo*) to do what I was describing, or
> (|^foo) which makes sense only if you either know very little about
> regular expressions or you realize that zsh prefers the leftmost of
> "|" alternatives over the longest of alternatives.
>
I can only guess what the parsing engine for this stuff looks like
and what immortal wrote it.
next prev parent reply other threads:[~2015-10-16 6:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 18:28 backreferences Ray Andrews
2015-10-15 23:16 ` backreferences Bart Schaefer
2015-10-16 1:16 ` backreferences Ray Andrews
2015-10-16 2:30 ` backreferences Bart Schaefer
2015-10-16 4:11 ` backreferences Mikael Magnusson
2015-10-16 4:27 ` backreferences Kurtis Rader
2015-10-16 5:42 ` backreferences Ray Andrews
2015-10-16 5:05 ` backreferences Bart Schaefer
2015-10-16 5:28 ` backreferences Bart Schaefer
2015-10-16 5:46 ` Ray Andrews [this message]
2015-10-16 11:14 ` backreferences Peter Stephenson
2015-10-16 5:36 ` backreferences Ray Andrews
2015-10-16 12:35 ` backreferences Bart Schaefer
2015-10-16 16:37 ` backreferences Ray Andrews
2015-10-17 3:33 ` backreferences Bart Schaefer
2015-10-17 5:16 ` backreferences Ray Andrews
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=56208F3A.1040706@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-users@zsh.org \
/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).