From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10584 invoked by alias); 26 Nov 2014 16:38:30 -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: 33802 Received: (qmail 24876 invoked from network); 26 Nov 2014 16:38:28 -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=AKpDk7pY 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=BrDiTsk0AAAA:8 a=zyK4wEy27qru4fSVnCQA:9 a=CjuIK1q_8ugA:10 From: Bart Schaefer Message-id: <141126083746.ZM23932@torch.brasslantern.com> Date: Wed, 26 Nov 2014 08:37:46 -0800 In-reply-to: <20141126154544.58ed6010@pwslap01u.europe.root.pri> Comments: In reply to Peter Stephenson "Re: Confirming X02zlevi test failures" (Nov 26, 3:45pm) References: <141119085006.ZM18951@torch.brasslantern.com> <11014.1416438322@quattro> <141119222019.ZM2717@torch.brasslantern.com> <5A1A98B7-42E0-4EE1-9468-32E2D6434246@kba.biglobe.ne.jp> <141120091803.ZM3693@torch.brasslantern.com> <900E2DDB-B03E-4E1F-9F22-869D5A645E52@kba.biglobe.ne.jp> <30162.1417013479@thecus.kiddle.eu> <20141126154544.58ed6010@pwslap01u.europe.root.pri> 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 26, 3:45pm, Peter Stephenson wrote: } Subject: Re: Confirming X02zlevi test failures } } On Wed, 26 Nov 2014 15:51:19 +0100 } Oliver Kiddle wrote: } > The delayzsetterm stuff is not related. Digging through the history } > shows that the "some systems" on which the workaround was needed are } > DG/UX and Ultrix. Any objections to just ripping this out as per the } > patch below? } } Sounds sensible to me, unless someone can dredge up a modern system like } this. It shouldn't be hard to write a test case though it requires a person to drive it. Open /dev/tty, set icanon, sleep while the user enters some typeahead, set -icanon and then see if you can read the typeahead. Then try the icanon flop in the opposite order. It might even be possible to do it with a script and stty rather than a C program, although it might also require that all the frobbing and reading use the same (not a dup of the same) file descriptor.