Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: FW: Zsh 4.3.12 failure on OpenBSD
- X-seq: zsh-workers 29419
- From: Mikael Magnusson <mikachu@xxxxxxxxx>
- To: zsh-workers@xxxxxxx
- Subject: Re: FW: Zsh 4.3.12 failure on OpenBSD
- Date: Wed, 1 Jun 2011 12:33:22 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=gq1u+G71Ogvtb8lFfzl+y0hC9CYHwb2HrvAc11AzS0w=; b=wAIpZu2Z4aSV2PvqnyUV67ogtG96Br0gaYEz73r3om8vWV14iCH/IY1AR2enn7hSDe VQj3buzu8SkA1xM0UsB7G7z2I3eiwjWEonfgb4OyExswA0r1GymeHuOZD1f0xwbW+L8s kCbgo4vTMr1LHbtgNUZMnuCSaWB/FW4VU/oxQ=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=tKbh4NvZZE+EkWFmKbt2IKsLcRTdA3cc1+qiameXIMMtgDDZV+7zYcqXQkuOeIlels R5DEO5UxBsJ6FBx2UjuKMOr7andB2nd3LN6Nwq3k6ZWtX/lxqa6jDtq3Wk0lRX/GVmJr 2DQsddSTCdrWhvK+Za54kAiU+bf3FvR8J43o4=
- In-reply-to: <FE1C78AF1864A242B1E74A21B8ED89973E5DC836@CAMEUREXM01.EUROPE.ROOT.PRI>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <20110601094642.GA32690@coredump.raveland.priv> <FE1C78AF1864A242B1E74A21B8ED89973E5DC836@CAMEUREXM01.EUROPE.ROOT.PRI>
On 1 June 2011 12:04, Peter Stephenson <Peter.Stephenson@xxxxxxx> wrote:
>
> ________________________________________
> From: Pierre-Emmanuel André [pea@xxxxxxxxxxxx]
> Sent: 01 June 2011 10:46
> To: Peter Stephenson
> Subject: Zsh 4.3.12 failure on OpenBSD
>
> Hi Peter,
>
> Sorry for the late feedback.
> I tried zsh-4.3.11-dev-3 on OpenBSD and there was no pbs.
> I didn't try dev-4 (no time).
> I wanted to update the OpenBSD port but i have a pb with
> regress tests on OpenBSD @amd64.
>
> ./D04parameter.ztst: starting.
> *** /usr/ports/pobj/zsh-4.3.12/zsh-4.3.12/tmp.ztst.out.24079 Wed Jun 1 11:40:42 2011
> --- /usr/ports/pobj/zsh-4.3.12/zsh-4.3.12/tmp.ztst.tout.24079 Wed Jun 1 11:40:42 2011
> ***************
> *** 1,6 ****
> eS
> eS
> e^X
> ! e^X\M-a
> eS^X
> ! e S ^X\M-a
> --- 1,6 ----
> eS
> eS
> e^X
> ! e^X�
> eS^X
> ! e S ^X�
> Test ./D04parameter.ztst failed: output differs from expected as shown above for:
> foo='\u65\123'
> print -r ${(g:o:)foo}
> foo='\u65\0123'
> print -r ${(g::)foo}
> foo='\u65^X'
> print -r ${(V)${(g:c:)foo}}
> foo='\u65\C-x\M-a'
> print -r ${(V)${(g:e:)foo}}
> foo='\u65\123\C-x'
> print -r ${(V)${(g:eo:)foo}}
> foo=('\u65' '\0123' '^X\M-a')
> print -r ${(V)${(g:e:)foo}}
> Was testing: ${(g)...}
> ./D04parameter.ztst: test failed.
Okay, so in a latin1 locale, \M-a is á which is printable, so it isn't
converted back to \M-a by (V). I also noticed that in one of the
tests, the input has "^X" but not the c flag, but does use V, so the
test can't tell if it was converted or not, because it'll always come
out as ascii "^X". I guess there's not really much point in testing
\M-a, since I already test \C-x and it's handled by the same code. The
test is just for calling the function that does that properly, not
that that function actually works ;). I hope I can at least rely on
\C-x not being printable anywhere? Or is it okay to include a literal
^X in the expected test output? I'm not sure how else I can test that
^X is parsed properly.
--
Mikael Magnusson
Messages sorted by:
Reverse Date,
Date,
Thread,
Author