From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6471 invoked by alias); 12 Sep 2015 20:35:46 -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: 36521 Received: (qmail 9628 invoked from network); 12 Sep 2015 20:35:46 -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=-1.9 required=5.0 tests=BAYES_00 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:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=L/r6JA8ihqf0MlbjAXGzEv9OXgmf2PClEaHzIlj/S8M=; b=MDG7GZvJv40MLtIe4OVxr6BuC2NfLm31A3GWHqNlft2Z5F4qNtI2EC+UvmqLh392xf HoTyafPw2Bd40/YdI2Fj0TG6i3qzMwYR2x02oMDiWS6Xoyye7QkVr7hd2Q3EE5g+538B 1HMwjjChumSJBkv9Q36f5m1iFtlY60IhLsjPHNq7ca/mUgMxEdKFUjHYX9wUP1p7kb3l b5dJrAtIWBrYdUyWv1LL67ipiPg71q7hmx/zP537a73RmqeAqx3087d3C5tFWue2IzSw 88jW75yuUeuy+tf6qqx4yV7in8PDwsg6bg8ZfE++ZkH/KQJZnLGE6HrPF5zDdpthSJ+r Tgmw== X-Gm-Message-State: ALoCoQmTBfWYM8XvPcUcQ0ZEKlwAx8eiCKspyCl/T6ioaJZqcu2UEv6hdLk8JS+r3fllmhOPcm2F MIME-Version: 1.0 X-Received: by 10.152.21.37 with SMTP id s5mr5088343lae.118.1442090143423; Sat, 12 Sep 2015 13:35:43 -0700 (PDT) In-Reply-To: <9wl4rxcdnmx1pobphlhpr6r7.1442088207988@email.android.com> References: <9wl4rxcdnmx1pobphlhpr6r7.1442088207988@email.android.com> Date: Sat, 12 Sep 2015 13:35:43 -0700 Message-ID: Subject: Re: PATCH: read full multibyte string a bit more sooner From: Bart Schaefer To: Peter Stephenson Cc: Zsh hackers list Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Sat, Sep 12, 2015 at 1:07 PM, Peter Stephenson wrote: > Certainly sounds like it thinks you're in some 16-bit locale. That doesn't explain why there's a sensible result with self-insert instead of with read-command. I think I've got this narrowed down now; this reproduces it: burner% zfoo() { zle -U '=C4=84 =D0=9F=D1=91=D1=82=D1=80 =D0=98=D0=BB=D1=8C= =D0=B8=D1=87 =D0=A7=D0=B0=D0=B9=D0=BA=D0=BE=D0=B2=D1=81=D0=BA=D0=B8=D0=B9 = =E6=A2=B6=E6=B5=A6=E7=94=B1=E8=A8=98' } burner% zle -N zfoo burner% =C4=83 =D0=83=D1=83=D1=82=D1=80 =D0=83=D0=BB=D1=83=D0=B8=D1=83 =D0=A7=D0=B0= =D0=B9=D0=BA=D0=BE=D0=B2=D1=81=D0=BA=D0=B8=D0=B9 =E6=A2=B6=E6=B5=A6=E7=83=B4=E8=A8=83 (esc-x zfoo ret after the zle -N) So it's specific to reading bytes out of (or putting them into) the kungetb= uf.