zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: <zsh-workers@zsh.org>
Subject: Re: zsh 5.6 regression: a pipe sometimes yields a TTOU signal
Date: Wed, 5 Sep 2018 11:03:54 +0100	[thread overview]
Message-ID: <20180905100356eucas1p29702acd7569a94c8c78003e6b124daaa~ReNxz4yht0327203272eucas1p2s@eucas1p2.samsung.com> (raw)
In-Reply-To: <20180905090339.GA18116@cventin.lip.ens-lyon.fr>

On Wed, 5 Sep 2018 11:03:39 +0200
Vincent Lefevre <vincent@vinc17.net> wrote:
> After the upgrade to zsh 5.6 under Debian/unstable, I sometimes get:
> 
> ypig:~> dpkg -l|gr mercurial  
> ii  mercurial                                                   4.7-1                                    amd64        easy-to-use, scalable distributed version control system
> ii  mercurial-common                                            4.7-1                                    all          easy-to-use, scalable distributed version control system (common files)
> zsh: exit 150
> zsh: suspended (tty output)  pager-wrapper grep --color=always --line-buffered -E mercurial
> ypig:~[TTOU]>  
> 
> where
> 
> gr: aliased to pager-wrapper grep --color=always --line-buffered -E
> 
> and pager-wrapper is:
> 
> pager-wrapper () {
>         local -a opt
>         while [[ $1 == -* ]]
>         do
>                 opt+=$1 
>                 shift
>         done
>         if [[ -t 1 ]]
>         then
>                 $@ $opt | less -+c -FRX
>         else
>                 $@
>         fi
> }

I managed to get this to happen once in a set of tests.

With

(echo mercurial) | gr mercurial

I always get

zsh: suspended (tty output)  pager-wrapper grep --color=always --line-buffered -E mercurial

This isn't going to be fixed quickly (or, quite likely, at all without
creating different knock-on effects, as changes here always do). Anyone
wanting to volunteer to look after job control would be very welcome ---
currently like so much of the shell it's down to when Bart and I
get a chance to look, as it has been for several decades now, which
isn't a sustainable position.

It's presumably down to the first job exiting and the other part
of the pipeline not getting control quickly enough.

pws



  reply	other threads:[~2018-09-05 10:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20180905091407epcas1p1ff78da39bfd4f3e4201f467683288a7b@epcas1p1.samsung.com>
2018-09-05  9:03 ` Vincent Lefevre
2018-09-05 10:03   ` Peter Stephenson [this message]
2018-09-05 10:55     ` Vincent Lefevre
2018-09-05 12:22       ` Vincent Lefevre
2018-09-05 13:17         ` Vincent Lefevre
2018-09-05 13:37           ` Vincent Lefevre
2018-09-05 14:40             ` Peter Stephenson
2018-09-06 11:40               ` Vincent Lefevre
2018-09-06 12:26                 ` Vincent Lefevre
2018-09-06 12:36                   ` Vincent Lefevre
2018-09-06 12:55                     ` Peter Stephenson
2018-09-05 12:53       ` Peter Stephenson
2018-09-05 13:21       ` Peter Stephenson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='20180905100356eucas1p29702acd7569a94c8c78003e6b124daaa~ReNxz4yht0327203272eucas1p2s@eucas1p2.samsung.com' \
    --to=p.stephenson@samsung.com \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).