From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: regexp-replace and ^
Date: Thu, 29 Oct 2015 16:46:35 -0700 [thread overview]
Message-ID: <151029164635.ZM18026@torch.brasslantern.com> (raw)
In-Reply-To: <20151029190807.GA18037@chaz.gmail.com>
On Oct 29, 7:08pm, Stephane Chazelas wrote:
}
} Or maybe have a (E) for ERE and (P) for PCRE parameter expansion flags
} for the ${var//pattern/replacement}.
Each of (E) and (P) already means something else.
It ought to be possible to fix regexp-replace. A leading "^" isn't that
difficult, it just means the loop should only go around once (unless you
expect it to match after embedded newlines). The tokens that match word
breaks require more thought. I'm not sure what to make of lookaheads.
next prev parent reply other threads:[~2015-10-29 23:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 19:08 Stephane Chazelas
2015-10-29 23:46 ` Bart Schaefer [this message]
2015-10-30 14:27 ` Stephane Chazelas
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=151029164635.ZM18026@torch.brasslantern.com \
--to=schaefer@brasslantern.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).