zsh-workers
 help / color / mirror / code / Atom feed
From: Frank Terbeck <ft@bewatermyfriend.org>
To: zsh-workers@zsh.org
Subject: Re: $pipestatus broken?
Date: Sun, 11 Dec 2011 15:37:10 +0100	[thread overview]
Message-ID: <87vcpnw4x5.fsf@ft.bewatermyfriend.org> (raw)
In-Reply-To: <111210065833.ZM6198@torch.brasslantern.com> (Bart Schaefer's message of "Sat, 10 Dec 2011 06:58:33 -0800")

Bart Schaefer wrote:
[...]
> With that loop, I get a single "1" 100% of the time unless I attach to
> the process with GDB, in which case it becomes random.

I know I won't be much help in solving this, because I don't know how
any of the job handling code works or even what needs to be done for any
sort of sane job handling in the first place...

But I tried to see if I could pinpoint the revision, that introduced the
breakage. And it appears, that the first release that featured
`$pipestatus' was 3.1.7. And it's broken in that release already.

The first tag that includes the feature is `zsh-3.1.6-dev-21'. I tried
to build it, but I can't get the autotools (I tried various versions) to
produce a valid `configure' script. :-/

`$pipestatus' was introduced in workers-10358:

  <http://www.zsh.org/mla/workers/2000/msg01183.html>

Regards, Frank


  reply	other threads:[~2011-12-11 14:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-10 12:24 Frank Terbeck
2011-12-10 12:48 ` Frank Terbeck
2011-12-10 14:58   ` Bart Schaefer
2011-12-11 14:37     ` Frank Terbeck [this message]
2011-12-23 10:49     ` Frank Terbeck
2011-12-23 21:31       ` Bart Schaefer
2011-12-23 22:11         ` Frank Terbeck
2011-12-24  9:32           ` Bart Schaefer
2011-12-24  9:59             ` Frank Terbeck
2011-12-24 18:23               ` Bart Schaefer
2011-12-24 18:46                 ` Bart Schaefer
2011-12-24 17:37       ` Bart Schaefer

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=87vcpnw4x5.fsf@ft.bewatermyfriend.org \
    --to=ft@bewatermyfriend.org \
    --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).