From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-workers@zsh.org
Subject: Re: make check problem
Date: Thu, 22 Jan 2015 10:24:43 -0800 [thread overview]
Message-ID: <54C1406B.40102@eastlink.ca> (raw)
In-Reply-To: <150122095610.ZM11712@torch.brasslantern.com>
On 01/22/2015 09:56 AM, Bart Schaefer wrote:
> I've said before that "not available" is not a "fault." You're reading
> way too much into "make check" skipping a test.
Sure. But it's difficult to know what's important there and what is
not. I get the feeling that this pcre isn't important, still one might
consider 'not available' to be something to worry about if you didn't
know it wasn't, since one might ask why it's checked if it *isn't*
important. (Or checked at all if it is explicitly not available.)
> It's special because it's extremely non-standard and changes the meaning
> of the expressions on the right-hand-side of the =~ comparison, so if
> unknowingly enabled it might break scripts.
Ok thanks. Looks like I don't want it anyway. At this point it's an
exercise.
Patch: ...
Testing PCRE multibyte with locale en_US.UTF-8
./V07pcre.ztst: all tests successful.
...
**************************************
43 successful test scripts, 0 failures, 0 skipped
**************************************
Navy clean ;-)
next prev parent reply other threads:[~2015-01-22 18:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-17 0:19 completion Ray Andrews
2015-01-17 2:57 ` Command substitution parsing issues (not really Re: completion) Bart Schaefer
2015-01-17 3:29 ` Ray Andrews
2015-01-17 13:25 ` Vin Shelton
2015-01-19 10:29 ` Peter Stephenson
2015-01-19 10:39 ` Peter Stephenson
2015-01-22 0:34 ` make check problem Ray Andrews
2015-01-22 8:49 ` Peter Stephenson
2015-01-22 16:00 ` Ray Andrews
2015-01-22 16:40 ` Jun T.
2015-01-22 17:38 ` Ray Andrews
2015-01-22 17:56 ` Bart Schaefer
2015-01-22 18:24 ` Ray Andrews [this message]
2015-01-23 4:02 ` Bart Schaefer
2015-01-23 4:48 ` Ray Andrews
2015-01-22 19:04 ` --enable-pcre and regex comparison (Was: make check problem) Lawrence Velázquez
2015-01-23 4:04 ` Bart Schaefer
2015-01-18 16:36 ` Command substitution parsing issues (not really Re: completion) Peter Stephenson
2015-01-18 17:31 ` Peter Stephenson
2015-01-18 22:34 ` Peter Stephenson
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=54C1406B.40102@eastlink.ca \
--to=rayandrews@eastlink.ca \
--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).