From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15141 invoked by alias); 1 Jun 2011 11:12:18 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 29420 Received: (qmail 20680 invoked from network); 1 Jun 2011 11:12:15 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW, SPF_HELO_PASS autolearn=ham version=3.3.1 Received-SPF: none (ns1.primenet.com.au: domain at csr.com does not designate permitted sender hosts) Content-Type: text/plain; charset="utf-8"; format=flowed; delsp=yes To: Subject: Re: FW: Zsh 4.3.12 failure on OpenBSD References: <20110601094642.GA32690@coredump.raveland.priv> Date: Wed, 1 Jun 2011 12:11:55 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable From: Peter Stephenson Organization: Cambridge Silicon Radio Message-ID: In-Reply-To: User-Agent: Opera Mail/11.11 (Win32) X-Originating-IP: [10.103.10.173] X-Scanned-By: MailControl A-10-80-00 (www.mailcontrol.com) on 10.68.0.123 On Wed, 01 Jun 2011 11:33:22 +0100, Mikael Magnusson =20= =20 wrote: > Okay, so in a latin1 locale, \M-a is =C3=A1 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. Ideally we want to output stuff as a stream of octets. I'm not sure there's an easy way of doing that with parameters alone. You can use $(( #foo )), looping over octets in the string. If you want to test non-ASCII characters you can use the multibyte test file, which ensures the locale is using UTF-8. pws Member of the CSR plc group of companies. CSR plc registered in England and= Wales, registered number 4187346, registered office Churchill House, Cambr= idge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom More information can be found at www.csr.com. Follow CSR on Twitter at http= ://twitter.com/CSR_PLC and read our blog at www.csr.com/blog