From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4110 invoked by alias); 23 Dec 2009 19:54:02 -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: 27541 Received: (qmail 14215 invoked from network); 23 Dec 2009 19:53:51 -0000 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VERIFIED autolearn=ham version=3.2.5 Received-SPF: pass (ns1.primenet.com.au: SPF record at _spf.google.com designates 74.125.78.146 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=p6C8c+82hrISZZREVCKYuCGix+WKLYdducN9OLAtrZk=; b=woQe5QAm9e3bwlert62z9wUVoTUxEyHkDStolqhLPq25H23QgmoifHzB0SOtzmVocx 811p9o/yz0siE8+70WfssQWCBbnPlp+I5qqVyDiTDf+rtc6pWOdQ6/zoKaX+sjRS1qhk FM8We9fu7mN341rFR9EU3e5kFLSWLhYRLMb0E= 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 :cc:content-type; b=G9ye3dJSJg5UUWBLkioMnOxkVcYZlvT4/MCHzWBOT3RAKiB4J7x+969b2F0jwVxslP HKhkhC/+zBU1m2ZdCZmtzrtQ967binI0G3wlbSI0CpCyQsUZYoMlXqv9RsmDgTEeunEQ yzsFlzjr+8yXRH6dHO756xze8hFZWlrkk5Pl0= MIME-Version: 1.0 In-Reply-To: <237967ef0912070258j45f4761brd8b809c8f50736e7@mail.gmail.com> References: <237967ef0912070258j45f4761brd8b809c8f50736e7@mail.gmail.com> Date: Wed, 23 Dec 2009 20:53:45 +0100 Message-ID: <2d460de70912231153y17005397y5ba6dbf88b69d83a@mail.gmail.com> Subject: Re: Entering zero-width chars in the ^r prompt messes up display From: Richard Hartmann To: Mikael Magnusson Cc: zsh workers Content-Type: text/plain; charset=UTF-8 On Mon, Dec 7, 2009 at 11:58, Mikael Magnusson wrote: > I pasted a filename from a webpage and it had some <200b> in it, so i > did ctrl-r ctrl-shift-200b to delete them quickly, but instead ended > up with weirdness. The same thing happens for combining chars like > <305>. Also notable is that the search seems to fail, while it works > fine for other utf-8 chars, including double-width japanese chars. I was unable to reproduce this but did not find anything explicit about this being fixed, etiher. Could you check again with current cvs? If it's still open, I will add it to the bug tracker. Richard