From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17717 invoked from network); 6 Sep 2000 12:51:57 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 6 Sep 2000 12:51:57 -0000 Received: (qmail 7861 invoked by alias); 6 Sep 2000 12:51:51 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 12754 Received: (qmail 7853 invoked from network); 6 Sep 2000 12:51:51 -0000 Date: Wed, 06 Sep 2000 13:51:23 +0100 From: Peter Stephenson Subject: Re: When should interactive option be set/.zshrc read? In-reply-to: "Your message of Wed, 06 Sep 2000 16:41:15 +0400." <000601c017ff$bedcbad0$21c9ca95@mow.siemens.ru> To: zsh-workers@sunsite.auc.dk (Zsh hackers list) Message-id: <0G0G00B57UDM35@la-la.cambridgesiliconradio.com> Content-transfer-encoding: 7BIT > I was sure, that my .zshrc was read only by interactice zsh, but > > bor@itsrm2% print $options[interactive] > on <= correct > bor@itsrm2% : | (print $options[interactive]) > on <= ?? I doubt, this shell can be considered "interactive" This is a completely different matter. The subshell inherits everything from the parent shell after the fork; it never re-initialiases. It does unset the options MONITOR and USEZLE, but not INTERACTIVE, for the subshell, however. One might have thought that it would either change all three or none. In particular, the effect of claiming to be interactive but not using ZLE looks a bit weird. Unless there is some standard behind this? -- Peter Stephenson Software Engineer Cambridge Silicon Radio, Unit 300, Science Park, Milton Road, Cambridge, CB4 0XL, UK Tel: +44 (0)1223 392070