From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21720 invoked by alias); 26 Nov 2014 05:43:59 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 19439 Received: (qmail 7364 invoked from network); 26 Nov 2014 05:43:57 -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=-2.6 required=5.0 tests=BAYES_00,HTML_MESSAGE, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=GzORopDeNyMQXWCbyXYBDGNgSYSP/KyfRUcMTxRwuhk=; b=LNknAGTwyKu7VJw8hzk1Puix6KnpXh7Fu8EcFiikY70IK83oJmLIq4VRnI4RslG9/V 42NK9pce+uv2jOAEn9HlaBPdgLyW7kd1o2MJPRPnfCIiXLpDugeUHu97UQL+ACnsIQt+ 8ivpiceqYDAzmyDZl5xY3epYFbxcx43P9MEjTqK41V+aUerXV39QvBzqxJPY6+E9ApQ7 NOk21/LJvZl2e3rJEQynk4HnZa0EKQU5o+duTUhZqlABHx7L2pDhTAL4621ncZn6f3iq 7Ku7btgr+iZdibHrRvWiodKhn2gafT2v+qAtOzvxl6mj+l/qm5ZoXNYd7DxcZQHs6yPl N6KQ== X-Gm-Message-State: ALoCoQlhmYpFs+a5LE9mi8Cb/ttNidU8zKzIi42Ip1jkg/epz4shEcDz7r7r++uDzJxurCL0MHNR MIME-Version: 1.0 X-Received: by 10.152.7.71 with SMTP id h7mr31268558laa.68.1416980633670; Tue, 25 Nov 2014 21:43:53 -0800 (PST) In-Reply-To: <54756007.6060800@eastlink.ca> References: <54752574.5090205@eastlink.ca> <141125203249.ZM18877@torch.brasslantern.com> <54756007.6060800@eastlink.ca> Date: Tue, 25 Nov 2014 21:43:53 -0800 Message-ID: Subject: Re: export From: Kurtis Rader To: Ray Andrews Cc: Zsh Users Content-Type: multipart/alternative; boundary=001a11c28fa052ec9a0508bc83db --001a11c28fa052ec9a0508bc83db Content-Type: text/plain; charset=UTF-8 Each process gets a private copy of the environment provided by its parent. An xterm is just a process. In your example you have this chain of processes (parent => child): xterm => zsh => zsh There is no way for an arbitrary zsh process to affect the environment of an arbitrary xterm process. On Tue, Nov 25, 2014 at 9:07 PM, Ray Andrews wrote: > On 11/25/2014 08:32 PM, Bart Schaefer wrote: > >> On Nov 25, 4:57pm, Ray Andrews wrote: >> } Subject: export >> } >> } When I export a variable it is only available in subsequent shells in >> } the same xterm. Can I make it export globally? >> >> > You guys don't understand what I'm asking. I know I can't pass > variables 'backwards' (except via a file), but when I export, the > variable will be available in *subsequent* shells but only in the > same xterm: > > pts/2 HP-y5--5-Debian1 root /aWorking/Zsh $ export trash=TRASH > > pts/2 HP-y5--5-Debian1 root /aWorking/Zsh $ zsh > > pts/2 HP-y5--5-Debian1 root /aWorking/Zsh $ echo $trash > TRASH > > ... export does what it should do, but *only* in the same xterm. > If I now go to another xterm, $trash is not set: > > pts/9 HP-y5--5-Debian1 root /boot/Clone/y8--5-Debian2 $ zsh > > pts/9 HP-y5--5-Debian1 root /boot/Clone/y8--5-Debian2 $ echo $trash > > > > -- Kurtis Rader Caretaker of the exceptional canines Junior and Hank --001a11c28fa052ec9a0508bc83db--