From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28193 invoked by alias); 12 Sep 2015 19:49:22 -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: 36517 Received: (qmail 21775 invoked from network); 12 Sep 2015 19:49:21 -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=1+JJPIepo3zGETNK6gGI/5iAhAF8pTkOjq4/QykE24k=; b=Z2/IVdaYw54hEH/t2wIb7XTFACDGNiVQIp65Cg8Nut/QYNAkcI4GcoulK3zpx7VYfo 9vx5EqUJKK1ww6lohygttZnHkKh3zZLKY+bNqeuiXkuwXvsmmeLnFKzmvO4eLN9xWTkX BnVbmC7d08EPdBainKlsh1N9VGYLJL7CI/5w6yOip0fHKN2i8zHtBw8zgMOPJkJUwfEn QM/ZvIWi6poFnXQcmYT7piPZVHHYWs4NDrVgg08LWraLa/mY2cRB1919ocVFTShmd7HF Iuo/Ug1Xu+CmkzoCNHRodcFD+cdWfVC6rU9ZH/hCWsVZAztOWCeKaTQQwdQ9TVYKgudW 8F2w== X-Gm-Message-State: ALoCoQm7kruBKp0X1xAk259lfQgw8L/DWB55z8opIeCqh7T1TvgSk8gx1FY8pAKX8j5GPetX6ltM MIME-Version: 1.0 X-Received: by 10.152.43.197 with SMTP id y5mr5029035lal.103.1442087358932; Sat, 12 Sep 2015 12:49:18 -0700 (PDT) In-Reply-To: <368flwd7fhj3wno0l0ybhfpk.1442086254641@email.android.com> References: <368flwd7fhj3wno0l0ybhfpk.1442086254641@email.android.com> Date: Sat, 12 Sep 2015 12:49:18 -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 12:41 PM, Peter Stephenson wrote: > >> ... if I step across >> getrestchar() with a debugger, it's failing on any character that >> is more than two bytes wide (returning only the first two bytes), > > getrestchar() only changed to the extent of passing back extra info. > It=CA=BCs being called at a different point but as long as the first byte= is > correct that shouldn't matter. Is that happening with 5.1.1? Yes, this appears also to happen with 5.1.1, which is why I began to suspect something external such as my LC_CTYPE value -- but I tried setting that to a couple of different non-English things and still have the same problem. mbrtowc() is always claiming a complete character after two bytes on that sample input.