From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20618 invoked from network); 6 Sep 2000 14:37:18 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 6 Sep 2000 14:37:18 -0000 Received: (qmail 20105 invoked by alias); 6 Sep 2000 14:36:52 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 12760 Received: (qmail 20098 invoked from network); 6 Sep 2000 14:36:51 -0000 Date: Wed, 06 Sep 2000 15:36:22 +0100 From: Peter Stephenson Subject: Re: When should interactive option be set/.zshrc read? In-reply-to: "Your message of Wed, 06 Sep 2000 17:23:49 +0400." <000801c01805$b10d35f0$21c9ca95@mow.siemens.ru> To: zsh-workers@sunsite.auc.dk (Zsh hackers list) Message-id: <0G0G00BNXZ8L35@la-la.cambridgesiliconradio.com> Content-transfer-encoding: 7BIT Andrej wrote: > "Environment" includes current option settings, aliases, functions > etc. SUS V2 shell supports job control, and has MONITOR option that is on > if shell is interactive. But it is silent on what happens with these > options in subshell. This probably means we've already broken it by unsetting MONITOR, in which case unsetting INTERACTIVE as well would be logical. However, it's not true that running in a subshell changes the basic feature of an interactive shell: standard input remains the tty, and the shell continues to read commands from the usual source --- unless, of course, the subshell is for some special purpose, such as a command substitution or part of a pipeline. But by that score we would have to unset INTERACTIVE when the current shell is running as the righthand side of a pipeline, which is clearly not on. So it's not all that clear cut. -- Peter Stephenson Software Engineer Cambridge Silicon Radio, Unit 300, Science Park, Milton Road, Cambridge, CB4 0XL, UK Tel: +44 (0)1223 392070