From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Cc: Sebastian Gniazdowski <sgniazdowski@gmail.com>
Subject: Re: $match size limit, suspicious (#B) behavior
Date: Mon, 17 Oct 2016 07:51:44 -0700 [thread overview]
Message-ID: <CAH+w=7Y76tDV+ubX-=VhAoP9E86kNcqZ4D8zs9AsyCaJzQQMRw@mail.gmail.com> (raw)
In-Reply-To: <CAKc7PVCt1BOU1_M_3AaRgnVDihKemJE0OQMmqY33BZXOhq0xEQ@mail.gmail.com>
[Sebastian Cc'd in case the list is still having indigestion over gmail MTAs]
On Sun, Oct 16, 2016 at 2:15 AM, Sebastian Gniazdowski
<sgniazdowski@gmail.com> wrote:
>
> Now code that matches either $var, ${var}, \$:
>
> while [[ "$mybuf" =
> (#b)([^\$\\]#)((#B)(\$([[:alpha:]_][[:alnum:]_]#|[[:digit:]]##)(\[[^[:space:]]#\])(#c0,1))|(\$[{](\([a-zA-Z0@%#]##\))(#c0,1)([[:alpha:]_][[:alnum:]_]#|[[:digit:]]##)(\[[^[:space:]]#\])(#c0,1)[}])|([\\][\'\"\$]))(#b)(*)
> ]]; do
>
> The problem: (#B) should have disabled all parentheses from where it
> is placed
What it looks like you're attempting to do is have
(#b)([^\$\\]#)((#B)....)(#b)(*) count as match[1] match[2] match[3]
without treating any of the more deeply nested parens inside the
match[2] pattern as backreferences?
That works with a very simple pattern:
% [[ 12345 = (#b)(?)((#B)(?)(?)(?))(#b)(?) ]]
% print -l :$^match
:1
:234
:5
The problem seems to be that the (#B) stops / (#b) implicitly resumes,
at the "|" in the second set of parens:
% [[ 12345 = (#b)(?)((#B)(?)|([[:alnum:]](#c0,1))(?))(#b)(*) ]]
% print -l :$^match
:1
:2
:
:
:345
If I add another set of parens around everything that follows (#B) up
to just before the close of the paren that opens before (#B), it looks
like what I expect:
% [[ 12345 = (#b)(?)((#B)((?)|([[:alnum:]](#c0,1))(?)))(#b)(*) ]]
% print -l :$^match
:1
:2
:345
next prev parent reply other threads:[~2016-10-17 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-16 9:15 Sebastian Gniazdowski
2016-10-16 9:40 ` Sebastian Gniazdowski
2016-10-17 14:51 ` Bart Schaefer [this message]
2016-10-17 15:00 ` Bart Schaefer
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='CAH+w=7Y76tDV+ubX-=VhAoP9E86kNcqZ4D8zs9AsyCaJzQQMRw@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=sgniazdowski@gmail.com \
--cc=zsh-workers@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).