From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11500 invoked by alias); 1 Sep 2014 18:28:42 -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: 33086 Received: (qmail 24223 invoked from network); 1 Sep 2014 18:28:38 -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 From: Bart Schaefer Message-id: <140901112837.ZM1866@torch.brasslantern.com> Date: Mon, 01 Sep 2014 11:28:37 -0700 In-reply-to: <20140901111643.6e2acd9b@pwslap01u.europe.root.pri> Comments: In reply to Peter Stephenson "Re: stty not working" (Sep 1, 11:16am) References: <140901012727.ZM1069@torch.brasslantern.com> <20140901111643.6e2acd9b@pwslap01u.europe.root.pri> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: stty not working MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Sep 1, 11:16am, Peter Stephenson wrote: } Subject: Re: stty not working } } Maybe we should be a bit more explicit about what ttyctl does and } doesn't do. ttyctl also doesn't "remember" the external stty state for assertion when the line editor finishes. E.g., I might have expected that % ttyctl -u; stty -echo; ttyctl -f would "freeze" the terminal in no-echo mode, such that when accept-line is run and ZLE finishes, the terminal would be put into no-echo mode before the command is run. But that's not what happens; "freeze" does not mean to lock the current state, it means to *block* changes made by subsequent commands. Which is what the doc says, but perhaps not clearly enough.