From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15895 invoked from network); 25 Mar 2001 23:58:14 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 25 Mar 2001 23:58:14 -0000 Received: (qmail 8354 invoked by alias); 25 Mar 2001 23:58:07 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 13760 Received: (qmail 8343 invoked from network); 25 Mar 2001 23:58:07 -0000 From: "Bart Schaefer" Message-Id: <1010325235757.ZM11718@candle.brasslantern.com> Date: Sun, 25 Mar 2001 23:57:57 +0000 X-Mailer: Z-Mail (5.0.0 30July97) To: zsh-workers@sunsite.dk Subject: Setting MONITOR after startup MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii While fooling with Ryan Richter's infinite-loop-bug, I happened to try running `zsh +m': zagzig% setopt interactive norcs shinstdin zle zagzig% setopt monitor zsh: can't set tty pgrp: operation not permitted zagzig% setopt monitor zagzig% sleep 10 & [1] 11706 zagzig% jobs [1] + running sleep 10 zagzig% [1] + done sleep 10 zagzig% Why did "setopt monitor" fail the first time, but not the second time? Also, I can't reproduce it now with "zsh -f +m" but at one point the entire shell got stopped with a SIGTTOU. This led me to notice that there's a lot of signal handling that's only done when `jobbing' is true when the shell first starts up; maybe some of that should be independent of `jobbing', or maybe it all needs to get done again somewhere else if the state of MONITOR changes? No patch yet ... -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net