From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5091 invoked from network); 17 Jul 1998 14:58:55 -0000 Received: from math.gatech.edu (list@130.207.146.50) by ns1.primenet.com.au with SMTP; 17 Jul 1998 14:58:55 -0000 Received: (from list@localhost) by math.gatech.edu (8.9.1/8.9.1) id KAA20332; Fri, 17 Jul 1998 10:52:50 -0400 (EDT) Resent-Date: Fri, 17 Jul 1998 10:52:50 -0400 (EDT) From: Zefram Message-Id: <199807171454.PAA10393@taos.demon.co.uk> Subject: Re: bug with chpwd/allexport To: dominik_vogt@hp.com (Dominik Vogt) Date: Fri, 17 Jul 1998 15:54:32 +0100 (BST) Cc: zefram@tao.co.uk, zsh-workers@math.gatech.edu In-Reply-To: <35AF5FB5.25F5@hp.com> from "Dominik Vogt" at Jul 17, 98 04:29:26 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"Lrd8v2.0.bz4.1Lshr"@math> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/4241 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu Dominik Vogt wrote: >OK, you're right, you can read the manpage this way, but it's just >implicitly in the description and not stated clearly. And I do not >understand why the ALLEXPORT option is handled differently in shell >functions if the auto-exported variables are not visible in the calling >environment anyway. You seem to be confusing the concepts of `existing outside the shell function' and `exported' (visible to programs invoked from the shell). The two are mostly, though not entirely, independent of each other. In particular, exporting a variable does nothing to extend its lifetime. > I think it just creates confusion about which >variables are exported to subshells of the function and which are not? All variables, exported or not, exist in subshells. -zefram