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 15:40:47 +0100	[thread overview]
Message-ID: <20180905144049eucas1p29a22151c8a47745343b899adefaa3fc2~Rh-iZ0O7_1601216012eucas1p2j@eucas1p2.samsung.com> (raw)
In-Reply-To: <20180905133704.GC4516@cventin.lip.ens-lyon.fr>

On Wed, 5 Sep 2018 15:37:04 +0200
Vincent Lefevre <vincent@vinc17.net> wrote:

> As a workaround, putting the middle command in { } can help a bit.
> For instance, instead of
> 
>   echo foo | { cat | less -+c -FX }
> 
> writing
> 
>   echo foo | { { cat } | less -+c -FX }
> 
> seems to avoid the issue most of the time, and
> 
>   echo foo | { { sleep 0.001; cat } | less -+c -FX }

If you don't actually care about where the command is run, I'd suggest
using ( ) instead of { } which should avoid the issue entirely ---
no "Rimmerworld" nested pipeline management as each pipe is in a
different shell.

pws


  reply	other threads:[~2018-09-05 14:41 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
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 [this message]
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='20180905144049eucas1p29a22151c8a47745343b899adefaa3fc2~Rh-iZ0O7_1601216012eucas1p2j@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).