zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: <zsh-workers@zsh.org>
Subject: Re: zsh fails 7 tests on ppc when built with --disable-unicode9 --disable-multibyte
Date: Tue, 7 May 2019 09:53:03 +0100	[thread overview]
Message-ID: <1557219183.6291.9.camel@samsung.com> (raw)
In-Reply-To: <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@mailbox.org> 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


      reply	other threads:[~2019-05-07  8:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-04 20:47 Erhard F.
2019-05-06  5:06 ` dana
2019-05-07  8:53   ` Peter Stephenson [this message]

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=1557219183.6291.9.camel@samsung.com \
    --to=p.stephenson@samsung.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).