From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-30004-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 2721 invoked by alias); 11 Dec 2011 23:39:54 -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: 30004
Received: (qmail 22973 invoked from network); 11 Dec 2011 23:39:52 -0000
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE
	autolearn=ham version=3.3.2
Received-SPF: none (ns1.primenet.com.au: domain at closedmail.com does not designate permitted sender hosts)
From: Bart Schaefer <schaefer@brasslantern.com>
Message-id: <111211153918.ZM32739@torch.brasslantern.com>
Date: Sun, 11 Dec 2011 15:39:18 -0800
In-reply-to: <20111211205658.365243c7@pws-pc.ntlworld.com>
Comments: In reply to Peter Stephenson <p.w.stephenson@ntlworld.com>
 "Re: Bug in sh emulation" (Dec 11,  8:56pm)
References:
 <CAG2tFJy+crpJVg2m1kO9H=fhYUYqPWEuJg+ivDaXCqzqOxa3Hg@mail.gmail.com>
	<111209184747.ZM5000@torch.brasslantern.com>
	<20111210194022.5051f91c@pws-pc.ntlworld.com>
	<20111210232801.7dc8fef2@pws-pc.ntlworld.com>
	<20111211193949.2d58062b@pws-pc.ntlworld.com>
	<20111211202024.07c046df@pws-pc.ntlworld.com>
	<20111211205658.365243c7@pws-pc.ntlworld.com>
X-Mailer: OpenZMail Classic (0.9.2 24April2005)
To: zsh-workers@zsh.org
Subject: Re: Bug in sh emulation
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii

On Dec 11,  8:56pm, Peter Stephenson wrote:
}
} What should happen:
} 
} - Fork for subshell as before
} 
} - attachtty() as before
} 
} - Shell keeps ignoring SIGTTOU because...
} 
} - MONITOR is left on for POSIXJOBs as this is a (...) subshell in the
}   foreground.
} 
} - Fork for pipeline
} 
} - attachtty() works because SIGTTOU is still ignored

I think there's a flaw here:  attachtty() doesn't *work*, in that it
won't actually associate the new process group with the TTY.  Instead
it just won't result in an infinite loop.
 
} - Now stop ignoring SIGTTOU because the pipeline element is not a (...)
}   subshell, it's some random command
} 
} - MONITOR is turned off for the same reason.

I think this will happen as a side-effect of attachtty() failing to do
any other useful work.  Does it not print the "can't set tty pgrp"
error?