From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21872 invoked by alias); 10 Sep 2015 16:28:51 -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: 36477 Received: (qmail 21659 invoked from network); 10 Sep 2015 16:28:48 -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-AuditID: cbfec7f5-f794b6d000001495-67-55f1afbb45e3 Date: Thu, 10 Sep 2015 17:28:40 +0100 From: Peter Stephenson To: zsh-workers@zsh.org Subject: Re: Pasting UTF-8 characters with bracketed-paste-magic seems broken in 5.1 Message-id: <20150910172840.0a1899f4@pwslap01u.europe.root.pri> In-reply-to: <150910091649.ZM3715@torch.brasslantern.com> References: <20150906155751.GD3721@sym.noone.org> <150910073920.ZM21998@torch.brasslantern.com> <20150910145714.GO3721@sym.noone.org> <150910084516.ZM22892@torch.brasslantern.com> <20150910170705.0fbeb302@pwslap01u.europe.root.pri> <150910091649.ZM3715@torch.brasslantern.com> Organization: Samsung Cambridge Solution Centre X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu) MIME-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrCLMWRmVeSWpSXmKPExsVy+t/xy7q7138MNdizVdLiYPNDJgdGj1UH PzAFMEZx2aSk5mSWpRbp2yVwZZyas4WtYCVHxY2z6g2M59m6GDk5JARMJLoabkDZYhIX7q0H srk4hASWMkp0TXjNAuHMYJJYeraXEcLZxihx9f4FFpAWFgFVie8Pf7OC2GwChhJTN81mBLFF BMQlzq49D1YjLBAmcbF9IlicV8Be4kHnIXYQm1PAUuLe+8NQG+YxSSw/0go2iF9AX+Lq309M EDfZS8y8cgaqWVDix+R7YEOZBbQkNm9rYoWw5SU2r3nLDGILCahL3Li7m30Co9AsJC2zkLTM QtKygJF5FaNoamlyQXFSeq6RXnFibnFpXrpecn7uJkZI2H7dwbj0mNUhRgEORiUe3oSLH0KF WBPLiitzDzFKcDArifCa930MFeJNSaysSi3Kjy8qzUktPsQozcGiJM47c9f7ECGB9MSS1OzU 1ILUIpgsEwenVAOjf90/Rv1El7wS4xtGv8ybPnM3S8UbXXa5GdWxuVxo0pou7/y/IXueTv92 +9yj1G1+W6ReL+vfvPvAbGFjdVcp3suKLa8i1irHvRVODEjROh4xbZXYHTN9ueyofaxn0sTn mv5cfW/R5nWW/b5uC668PH7krPBpWWnXxwoB1+Zv7DR5/reAScteiaU4I9FQi7moOBEAU/a/ clcCAAA= On Thu, 10 Sep 2015 09:16:49 -0700 Bart Schaefer wrote: On Sep 10, 5:07pm, Peter Stephenson wrote: > } > } read-command doesn't explicitly handle multibyte characters in the way > } self-insert does. self-insert gets the remainder of the character. > > Hrm. So the problem is that a multibyte character isn't explicitly > bound to self-insert, rather the first byte is bound to self-insert > and self-insert knows that when it sees that byte it should read more? Right. > Should be possible to handle that in the loop in bracketed-paste-magic > with a test of $KEYS and a call to read -k. Might try to get to this > later, out of time now ... or someone else can jump in. Not really clear to me what level the "right" fix is, since this was all designed for a pre-multibyte world... I don't think we have a test for a valid/invalid multibyte character at the shell level currently, do we? Wouldn't be hard to add [[:INCOMPLETE::]] or [[:INVALID:]] to the pattern code, but that's an extra step... pws