From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28650 invoked by alias); 20 Nov 2014 17:17:40 -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: 33725 Received: (qmail 11277 invoked from network); 20 Nov 2014 17:17:40 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=Cp8Iqc8G c=1 sm=1 tr=0 a=FT8er97JFeGWzr5TCOCO5w==:117 a=kj9zAlcOel0A:10 a=q2GGsy2AAAAA:8 a=oR5dmqMzAAAA:8 a=-9mUelKeXuEA:10 a=5y4faFyK3SkA:10 a=DU3sIWwu79qAjNqiGJwA:9 a=CjuIK1q_8ugA:10 From: Bart Schaefer Message-id: <141120091803.ZM3693@torch.brasslantern.com> Date: Thu, 20 Nov 2014 09:18:03 -0800 In-reply-to: <5A1A98B7-42E0-4EE1-9468-32E2D6434246@kba.biglobe.ne.jp> Comments: In reply to "Jun T." "Re: Confirming X02zlevi test failures" (Nov 21, 12:42am) References: <141119085006.ZM18951@torch.brasslantern.com> <11014.1416438322@quattro> <141119222019.ZM2717@torch.brasslantern.com> <5A1A98B7-42E0-4EE1-9468-32E2D6434246@kba.biglobe.ne.jp> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: Confirming X02zlevi test failures MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Nov 21, 12:42am, Jun T. wrote: } } Next I replaced TCSADRAIN by TCSANOW in settyinfo() (utils.c, line 1554), } and now 'swap case on a blank line' in X02zlevi.ztst seems to succeed. } But I don't know what kind of unwanted side effects it may cause. It'll cause typeahead to be misinterpreted when using a "real" terminal device, I fear. It took a lot of work back in the day to get that tty draining stuff right. } Moreover, if 'werase undef' is removed from comptest, line 37, then } X02zlevi.ztst fails again at } 'line based put before followed by character based yank-pop'. I begin to suspect that what needs to happen is that zpty needs to be a lot more aggressive internally about consuming (and buffering up) the slave output as fast as it appears, even if a zpty read call has not yet been made from the shell. Clearly the slave can "see" it's own output if the master doesn't manage to grab it first.