From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14351 invoked by alias); 10 Jun 2015 05:32:03 -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: 35430 Received: (qmail 24606 invoked from network); 10 Jun 2015 05:32:02 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) 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, RCVD_IN_MSPIKE_H2 autolearn=ham autolearn_force=no version=3.4.0 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version:content-type; bh=jtjBCRKqNu3MJCcVP6YAKX94tdVuJLUMcfwYYP+x51c=; b=cLUNdT7EtFOLxOWLqNHhe3OFNYCx/o0TXxaarY66oRusNEw8EPAlF90i54jhjSOiMP G3dLZWZgOVL+ajLdonRC0qAmjherWviP15WJA6prZup1Bpc05tU7pGBYQuHZa2A1Uv3N EJN8gFn7llaqghGkT0G0lzf3DwQqds8g5d9hF4AMaZJp8OhMWaBTS1pQGVH9CgznOOTy PbXXx5jHIAWCGAVwR2BK8DUx5vyPLhttSOtFA7nlC7vNo5+enTQKx2f+cf4Arn18cjKz 1xKymQNxeodsGKgPeCbhWBB+kYgrTqUA90HVArQazfU+7yy5LUJTGeOo174D0pTeabj5 JCdQ== X-Gm-Message-State: ALoCoQmcjbpU9ePZDb145EIG/WRqvFK7jTrQgd8AfPP6rV72zUFKO4JY26vOX45Xk3viDS8Qdkgv X-Received: by 10.202.172.16 with SMTP id v16mr1082286oie.51.1433914320515; Tue, 09 Jun 2015 22:32:00 -0700 (PDT) From: Bart Schaefer Message-Id: <150609223156.ZM29890@torch.brasslantern.com> Date: Tue, 9 Jun 2015 22:31:56 -0700 In-Reply-To: <5577AE8F.6060902@arthaud.me> Comments: In reply to Maxime Arthaud "Strange behavior of [[" (Jun 9, 8:27pm) References: <5577AE8F.6060902@arthaud.me> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: Strange behavior of [[ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Jun 9, 8:27pm, Maxime Arthaud wrote: } Subject: Strange behavior of [[ } } Hi everybody! } } I just found a very strange behavior in zsh (v5.0.8). } } % [[ " X" =~ "X" ]] } where in " X" the first character is a non-breaking space (0xa0). } My shell gets stuck, and Ctrl-C is not working. With bash, no problem. } } Does anyone have an explanation? I think it's a bug. MB_METACHARLEN() is returning that 0xa0 is a zero-width character, so "ptr" in the "while (ptr < lhstr + m->rm_so)" loop in regex.c never advances. That macro ultimately resolves to mb_metacharlenconv_r() from utils.c, which returns zero here: 4861 return 0; /* Probably shouldn't happen */ This means that imeta() is (incorrectly?) returning true for 0xa0, which might mean that we're passing an unmetafied string where a metafied string is expected.