From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-36014-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 13613 invoked by alias); 8 Aug 2015 20:40:08 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 36014
Received: (qmail 10437 invoked from network); 8 Aug 2015 20:40:05 -0000
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,HTML_MESSAGE,
	RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham
	autolearn_force=no version=3.4.0
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:mime-version:in-reply-to:references:date
         :message-id:subject:from:to:content-type;
        bh=Rhw7BVZmm6JDM6JIH3KWuUHLKSH+MeNGsxOIrwCf59U=;
        b=KO+MvcBra3XwzscxDy0Uvol7l+Lu/EkLEzT7Hm4c+BCugIXwnYChLA6DKmebhP9xtc
         XgQ3RfkXNAcJyfdAar10R5hTEnrsj4LytWsM+pFqGOwjSk4VGuE+464c6ziR4p5t2zv0
         bUrtbdGg2PhN6aG2AUycneUMxLyDfrKKJ3ZrzVCr2HLXf1SeqQFmWYwK3CVOFxdOO/6H
         6iPM9AgSQtNI3/Kw6B0BtxZsVevZ3zRGHpPlAa8JK8HEetpTMz34WQQ/III66ZTuy5sO
         5w96mhZbdrNtKZ1hbtvPUfNLVUy17/V/CryCQ1wmclH3J2yixLpEBZZ7nwuRZV6SJG3/
         vrQA==
X-Gm-Message-State: ALoCoQlvYQ1PX9APfvGX+9fIl4/htQQNHhtgdsitH8DmOkbOPymT2VCypHE8nQ3DEnKMTAsVRu6k
MIME-Version: 1.0
X-Received: by 10.194.71.165 with SMTP id w5mr25172172wju.135.1439066400988;
 Sat, 08 Aug 2015 13:40:00 -0700 (PDT)
In-Reply-To: <20150808200521.4e3c85d1@ntlworld.com>
References: <20150808200521.4e3c85d1@ntlworld.com>
Date: Sat, 8 Aug 2015 13:40:00 -0700
Message-ID: <CAH+w=7aqD4D+iAbFV4-xv+8HgAF2Q4rdEoov2z0+A96Ycf59Eg@mail.gmail.com>
Subject: Re: 5.0.9 eventually...?
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Content-Type: multipart/alternative; boundary=047d7bfcef9ea3b591051cd2c170

--047d7bfcef9ea3b591051cd2c170
Content-Type: text/plain; charset=UTF-8

On Aug 8, 2015 12:11 PM, "Peter Stephenson" <p.w.stephenson@ntlworld.com>
wrote:
>
> Anyone (including Bart, obviously) with a feel for what's the state of
> affairs with regards to immediate problems?

Nothing has been done about the infinite loop with "wait" printing the job
status.  After pointing out that ksh and bash differ in wait
implementation, I got distracted by the signal handing deadlock thread.

I have what I think is a comprehensive patch for that signal issue but am
AFK today (writing this message on my phone).  Will post later.

I posted a sort-of patch for the "typeset -T" crash, but I agree that it is
not the ideal solution.

That's as much as I'm aware of from memory.

--047d7bfcef9ea3b591051cd2c170--