From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: backreferences
Date: Fri, 16 Oct 2015 05:35:55 -0700 [thread overview]
Message-ID: <151016053555.ZM31602@torch.brasslantern.com> (raw)
In-Reply-To: <56208CF8.1070906@eastlink.ca>
On Oct 15, 10:36pm, Ray Andrews wrote:
}
} > if [[ "$sstring" = (#b)((^(edcba))*)(edcba)(*) ]]
} >
} > There are 5 sets of parens, and you care about $match[1], $match[4],
} > and $match[5]. $match[2] is the prefix of $match[1] that was not
} > consumed by the middle *, and $match[3] is an empty substring of
} > $match[2] (because it was excluded from matching). Count off the
} > open parens left to right to see this.
} At the moment I'm quite confounded. So '(b#)' is looking at every set
} of '()' even
} when nested and even when 'doing something else'?
Yes.
} > In fact you don't even need the middle * because (^edcba) will eat
} > an arbitrarily long string as long as it is not literally "edcba".
} Well, that's the original question.
As noted in my follow-up mail, what I wrote there is actually not right;
the part after "because" is correct, but the part about not needing the
middle * is wrong, because (^edcba) matches xxxxedcbaxxxx just fine, and
I assume you don't want that.
} > So you can reduce this to
} >
} > if [[ "$sstring" = (#b)(^edcba)(edcba)(*) ]]
This needs to be (#b)(^edcba*)(edcba)(*)
} God knows. But your simplified command works fine too, and I'll
} take it on faith. I've never seen any sort of 'any number of characters'
} sort of thing look other than:
} [....]*
No, now you're confusing grep-style regular expressions with zsh patterns.
EGREP ZSH
. ?
.* * or ?#
.+ ?##
.? (?|)
[xyz] [xyz]
[xyz]* [xyz]#
There's a lot more but those are the most important bits.
} ... so you can see where I'd go astray there. Ok, so
} ^(edcba)
} is individual character matches and
} (^edcba)
} is anything up to "edcba"
No. [^edcba] is individual character matches and (^edcba) is anything
other than the literal string edcba, including longer strings that have
edcba as a substring. Negated patterns are really tricky.
next prev parent reply other threads:[~2015-10-16 12:36 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 ` backreferences Ray Andrews
2015-10-16 11:14 ` backreferences Peter Stephenson
2015-10-16 5:36 ` backreferences Ray Andrews
2015-10-16 12:35 ` Bart Schaefer [this message]
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=151016053555.ZM31602@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--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).