From: Kurtis Rader <krader@skepticism.us>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: export
Date: Tue, 25 Nov 2014 21:54:08 -0800 [thread overview]
Message-ID: <CABx2=D8G70KVTBaTXkojxmqn6bKYp_VX=e7AdO=obbd2c543UA@mail.gmail.com> (raw)
In-Reply-To: <CABx2=D8gHmuPv+asZ6-S5d+gLfEy09WJwAgFoU_epNh-iJ34Nw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2127 bytes --]
In general a process, whether it is a zsh or other program, cannot affect
the environment of any other program. It can only provide the initial state
for a new program that it executes. That is what is happening in your
example. You are interacting with a zsh process spawned by a xterm. In that
zsh process you modify its environment. You then spawn a new shell which
inherits a private copy of that environment.
There is no way to modify the private copy a given process has of its
environment.
On Tue, Nov 25, 2014 at 9:43 PM, Kurtis Rader <krader@skepticism.us> wrote:
> 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 <rayandrews@eastlink.ca>
> 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
>
--
Kurtis Rader
Caretaker of the exceptional canines Junior and Hank
next prev parent reply other threads:[~2014-11-26 5:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 0:57 export Ray Andrews
2014-11-26 2:36 ` export Eric Cook
2014-11-26 2:58 ` export Kurtis Rader
2014-11-26 4:32 ` export Bart Schaefer
2014-11-26 4:54 ` export Kurtis Rader
2014-11-26 5:16 ` export Ray Andrews
2014-11-26 5:38 ` export Kurtis Rader
2014-11-26 5:07 ` export Ray Andrews
2014-11-26 5:43 ` export Kurtis Rader
2014-11-26 5:54 ` Kurtis Rader [this message]
2014-11-26 17:43 ` export Ray Andrews
2014-11-26 18:26 ` export Павлов Николай Александрович
2014-11-26 18:45 ` export Ray Andrews
2014-11-26 5:50 ` export Павлов Николай Александрович
2014-11-26 6:21 ` export Kurtis Rader
[not found] ` <CABx2=D_zLTkdFsV+eT-VrwwaJQYr=1JeZF0eNqH44saPDYMD7Q__49907.9755544246$1416977797$gmane$org@mail.gmail.com>
2014-11-26 7:18 ` export Stephane Chazelas
2014-11-26 13:37 ` export Clint Hepner
2014-11-26 9:27 ` export Peter Stephenson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABx2=D8G70KVTBaTXkojxmqn6bKYp_VX=e7AdO=obbd2c543UA@mail.gmail.com' \
--to=krader@skepticism.us \
--cc=rayandrews@eastlink.ca \
--cc=zsh-users@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).