From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22281 invoked by alias); 12 Oct 2014 18:03: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: 33447 Received: (qmail 23962 invoked from network); 12 Oct 2014 18:03:49 -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.8 required=5.0 tests=BAYES_00,FROM_12LTRDOM, RCVD_IN_DNSWL_NONE,T_MANY_HDRS_LCASE autolearn=no version=3.3.2 From: Bart Schaefer Message-id: <141012110417.ZM23829@torch.brasslantern.com> Date: Sun, 12 Oct 2014 11:04:17 -0700 X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Misc. other USEZLE / SHINSTDIN notes MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Bash, at least as of (patched for shellshocker) version 3.00, so I guess this really means GNU readline, will happily read from one tty and write to another, including prompting and echoing on tty1 what is being typed on tty2. This is as easy as redirecting stdin from the second terminal. Zsh with ZLE enabled forcibly directs all editor interaction including the prompt to the same tty as the standard input; stdout and stderr including XTRACE and command output still go to the original tty. Zsh with ZLE off behaves like bash except that typed input echoes on the same tty where it is typed because there's no editor to stty -echo. Both behave as above regardless of whether stdin is redirected at time of invocation or with "exec 0