Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: zsh fails 7 tests on ppc when built with --disable-unicode9 --disable-multibyte
- X-seq: zsh-workers 44277
- From: Peter Stephenson <p.stephenson@xxxxxxxxxxx>
- To: <zsh-workers@xxxxxxx>
- Subject: Re: zsh fails 7 tests on ppc when built with --disable-unicode9 --disable-multibyte
- Date: Tue, 7 May 2019 09:53:03 +0100
- Cms-type: 201P
- Dkim-filter: OpenDKIM Filter v2.11.0 mailout2.w1.samsung.com 20190507085306euoutp022543850b719640a0d294737c2f2cc953~cWpmHANiW1808618086euoutp02N
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samsung.com; s=mail20170921; t=1557219186; bh=gJiZPwgnDPRy6gUR9sX7E5RzBGdGYNYqmdN1Fy/Eyi4=; h=Subject:From:To:Date:In-Reply-To:References:From; b=j0CLcB5S17zevJUIbY83e9y7KGhnIKRWaIm44pkjR1npAc6yYjw3Kh/dHW4i9TySB dOJHMHLAbUjaB+qpf259iEFDYUQkMGBwdJ8TWsmvocT0XelJJyRWp1Qv/TRuf81ZaK GlF6Ckjb+iUOsm5EBk7l+oI0XJocfMPNkvmjvF0Y=
- In-reply-to: <049B61FC-A15F-4206-B3C3-29C5B54FBDB1@dana.is>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- List-unsubscribe: <mailto:zsh-workers-unsubscribe@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <20190504224734.39ff64ff@supah> <CGME20190506050610epcas3p3825901b97f89dac4295a38fcf10b0f76@epcas3p3.samsung.com> <049B61FC-A15F-4206-B3C3-29C5B54FBDB1@dana.is>
On Mon, 2019-05-06 at 00:06 -0500, dana wrote:
> On 4 May 2019, at 15:47, Erhard F. <erhard_f@xxxxxxxxxxx> wrote:
> >
> > I found the testsuite fail the following tests when zsh 5.7.1 is built with
> > --disable-unicode9 --disable-multibyte:
> Most of these failures are the result of a deliberate choice, mentioned in
> workers/37304, not to apply fancy quoting when the shell has no multi-byte
> support. The affected tests don't account for this difference. (Also, it isn't
> documented under e.g. Parameter Expansion Flags)
>
> I'm not sure how much effort is meant to be expended on tests for uncommon
> configurations, but we do account for non-multi-byte shells in a few test
> files already; i suppose we could do the same for these. If we do, maybe we
> should build a multi-byte detection function into ztst rather than copy/paste
> it into each individual file. I can look into it later if there are no other
> ideas/preferences
Something like that would be very helpful to sanity check this case.
Uncommon configurations aren't necessarily tested for and removing
multibyte support completely isn't something you'd expect people to do
for anything other than very special uses. Even so, the pre-multibyte
code is a significant set of code in its own right so if we can test it
so much the better.
Cheers
pws
Messages sorted by:
Reverse Date,
Date,
Thread,
Author