From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12001 invoked by alias); 30 Jul 2015 19:39:15 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 35958 Received: (qmail 14491 invoked from network); 30 Jul 2015 19:39:12 -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,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:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version:content-type; bh=UbQEZ37k8A/B810grF4H0zT22mk3stM5L2OYvWpPeO8=; b=N3TYOKgfiml7YNUx3MyU15/ZoObf9n9/ipGmI8PcIKFAfl5LAmCjtgmgYqcpzUy+sx e652JBZKaeds2eveLYaPTx1lSfHHDVVqA3zz8W+jfunTioc9BDwSdQWzOysYca5BdOjG Lp6aDLoudts+WaG70CbRQZo+9PyFdlyMvhAzHgxwMKvO+KC3sYSdo8U37BoENJbh7Mhs lZcw8U9StARC0LgW9Z1r6FrEatNxF/g3yVlAYNNTG+BFB3+BQP0Qll0z11v4lbbMX1+W +BoOFhn7/l3h3qjOvsBnpBCgS/ZZgyHLwvdqGOkGVV+ZmVlJqcfLTSDTVysqzKTMOaaI L5vA== X-Gm-Message-State: ALoCoQmUdTV6KG5Dkudhe0M8IV9uWDQXiP3jcJgHJTzHOCqq2MSfjC5sMCDcSamjumPgdwD08RAr X-Received: by 10.202.12.142 with SMTP id 136mr45208971oim.30.1438285149699; Thu, 30 Jul 2015 12:39:09 -0700 (PDT) From: Bart Schaefer Message-Id: <150730123904.ZM11774@torch.brasslantern.com> Date: Thu, 30 Jul 2015 12:39:04 -0700 In-Reply-To: <87wpxhk970.fsf@gmail.com> Comments: In reply to Christian Neukirchen "5.0.8 regression when waiting for suspended jobs" (Jul 30, 4:32pm) References: <87wpxhk970.fsf@gmail.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: 5.0.8 regression when waiting for suspended jobs MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Jul 30, 4:32pm, Christian Neukirchen wrote: } } Waiting for a job suspened with tty input results in an infinite loop } of messages in 5.0.8, but just one in 5.0.7. Hm. Both are busy-waiting, and I don't see the reason why 5.0.7 is NOT printing the job status every time. Also if you wait by job number ("wait %1") instead, "wait" returns right away rather than blocking on the stopped job (in both .7 and .8).