zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Failed pipeline doesn't err_exit/return if complex command last
Date: Sun, 16 Jul 2023 15:36:06 +0100	[thread overview]
Message-ID: <920e0f7cdb4eb59c3ee0d94efd7782cd84889e4b.camel@ntlworld.com> (raw)
In-Reply-To: <cf275400-d63a-d991-3aa5-1543d20a2f42@crans.org>

On Fri, 2023-07-14 at 20:31 +0200, Johan Grande wrote:
> Le 06/07/2023 à 11:44, Peter Stephenson a écrit :
> > > On 06/07/2023 00:18 Johan Grande <nahoj@crans.org> wrote:
> > > I noticed a strange behavior when using a complex command in a pipeline.
> > So in a nutshell
> 
> I'm curious about the process: whether the bug is likely going to be 
> fixed, and whether it's tracked somewhere public.
> 
> No urgency or pressure in my request, I'm just happy to follow up.

There's nowhere to look, other than this list --- if someone here doesn't
pick it up, no one is going to.

This area of the code has given a number of us sleepless nights over the
years, with many hours spent trying to resolve subtle job control issues,
so unless someone happens to spot some key clue, I doubt it's going anywhere
very fast.  Every now and then there are bursts of activity, however.

Cheers
pws


  parent reply	other threads:[~2023-07-16 14:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-05 23:18 Johan Grande
2023-07-05 23:45 ` Johan Grande
2023-07-06  9:44 ` Peter Stephenson
2023-07-08  4:31   ` Bart Schaefer
     [not found]   ` <cf275400-d63a-d991-3aa5-1543d20a2f42@crans.org>
2023-07-16 14:36     ` Peter Stephenson [this message]
2023-07-17 19:25       ` Johan Grande
2023-07-17 23:34   ` Bart Schaefer
2023-07-18  1:51     ` Bart Schaefer
2023-07-18 13:57       ` Peter Stephenson
2023-07-20  8:47         ` 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=920e0f7cdb4eb59c3ee0d94efd7782cd84889e4b.camel@ntlworld.com \
    --to=p.w.stephenson@ntlworld.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).