From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14905 invoked by alias); 26 Nov 2014 06:21:07 -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: 19442 Received: (qmail 13734 invoked from network); 26 Nov 2014 06:21:05 -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=VkgVpmhLtVGIJnfZZXLJ8f6OvZOODrLZ31xIDI0Tm6c=; b=hKGf89kYK4w1/wyTf10l8fpJnAxzpTLAWLTq6JzdS29D0vy9ey5/gQDhUAPTVGFxGz muoH+WViKYOD3htus7V5OGOvjpTdnFopeMVTT7gHCZrK8/LAjiKb6XOwQrHuwwBWrwg1 tTiMTBH0soe+cZuktSoRh0elvfEpl+gmMoSlQ4aOQy0CB3BphD+VmKyKHLSVTQ1n1UOA jAmJvwbFHLWlAe5y59g5krffZGBlsVITTEMvzI5Z5tyb5HWoiuU4UUNi9VO7yHW7bq+g WN+D0oEYH7Hi9Sh7eCvCCGvxBHk7tGlDdoQNLW37Sfn2qBL5mtC3lUTnvFfG04caDZ7F pvCg== X-Gm-Message-State: ALoCoQk1uoMBrX+GsAgOvk8ERDsd2iVIESo6mP4GJoVDzMqHBNEshEVJYeh1UcUwz40dPEZ5bB4t MIME-Version: 1.0 X-Received: by 10.152.203.199 with SMTP id ks7mr32128850lac.31.1416982861435; Tue, 25 Nov 2014 22:21:01 -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 22:21:01 -0800 Message-ID: Subject: Re: export From: Kurtis Rader To: Ray Andrews Cc: Zsh Users Content-Type: multipart/alternative; boundary=001a113470d41beb990508bd08fb --001a113470d41beb990508bd08fb Content-Type: text/plain; charset=UTF-8 FWIW, almost everyone, including me, has asked this question. That is, we've wished there was someway for a process to asynchronously modify the environment variables of another, arbitrary, process. There are good reasons from both a security as well as predicable execution model why that is a bad idea and therefore not allowed. 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 --001a113470d41beb990508bd08fb--