From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28306 invoked by alias); 5 Sep 2018 10:55:18 -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: List-Unsubscribe: X-Seq: 43383 Received: (qmail 19299 invoked by uid 1010); 5 Sep 2018 10:55:18 -0000 X-Qmail-Scanner-Diagnostics: from cventin.lip.ens-lyon.fr by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(140.77.13.17):SA:0(-1.9/5.0):. Processed in 2.825388 secs); 05 Sep 2018 10:55:18 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) 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 autolearn_force=no version=3.4.1 X-Envelope-From: vincent@vinc17.net X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Date: Wed, 5 Sep 2018 12:55:10 +0200 From: Vincent Lefevre To: zsh-workers@zsh.org Subject: Re: zsh 5.6 regression: a pipe sometimes yields a TTOU signal Message-ID: <20180905105510.GA2116@cventin.lip.ens-lyon.fr> Mail-Followup-To: zsh-workers@zsh.org References: <20180905090339.GA18116@cventin.lip.ens-lyon.fr> <20180905100356eucas1p29702acd7569a94c8c78003e6b124daaa~ReNxz4yht0327203272eucas1p2s@eucas1p2.samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20180905100356eucas1p29702acd7569a94c8c78003e6b124daaa~ReNxz4yht0327203272eucas1p2s@eucas1p2.samsung.com> X-Mailer-Info: https://www.vinc17.net/mutt/ User-Agent: Mutt/1.10.1+92 (9ed4bf53) vl-108074 (2018-09-02) On 2018-09-05 11:03:54 +0100, Peter Stephenson wrote: > With > > (echo mercurial) | gr mercurial > > I always get > > zsh: suspended (tty output) pager-wrapper grep --color=always --line-buffered -E mercurial Or just with: (echo foo) | { grep foo | less -+c -FX } > This isn't going to be fixed quickly (or, quite likely, at all without > creating different knock-on effects, as changes here always do). Is there any reason why this changed since zsh 5.5.1? If a new feature is the cause, couldn't it be reverted until this is fixed? -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)