From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: =~ doesn't work with NUL characters
Date: Wed, 14 Jun 2017 16:08:24 -0700 [thread overview]
Message-ID: <170614160824.ZM20324@torch.brasslantern.com> (raw)
In-Reply-To: <20170614204938.GA76510@tower.spodhuis.org>
On Jun 14, 4:49pm, Phil Pennock wrote:
}
} My personal inclination is to handle NULL in the PCRE case.
This harkens back to the discussion of whether =~ should implicitly
(i.e., by way of setopt) choose a regex package, or should always
mean the same thing.
Given that it's already doing the choose-implicitly thing, I have no
additional objection to it also handling nul bytes.
next prev parent reply other threads:[~2017-06-14 23:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 10:02 Stephane Chazelas
2017-06-14 20:49 ` Phil Pennock
2017-06-14 23:08 ` Bart Schaefer [this message]
2017-06-15 7:38 ` Peter Stephenson
2017-06-15 8:18 ` Stephane Chazelas
2017-06-15 9:50 ` 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=170614160824.ZM20324@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).