From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <140e7ec30911231833s73573dfbn23cf0ef0650ada5e@mail.gmail.com>
References: <a560a5d00911231424k7cfe7382v7a8339d8cf8376c6@mail.gmail.com>
	<140e7ec30911231833s73573dfbn23cf0ef0650ada5e@mail.gmail.com>
Date: Tue, 24 Nov 2009 09:34:12 +0100
Message-ID: <a560a5d00911240034p5744bcx343b4da4666b979b@mail.gmail.com>
From: Rudolf Sykora <rudolf.sykora@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: multipart/alternative; boundary=000e0cd296007a1194047919cedf
Subject: Re: [9fans] environment variables
Topicbox-Message-UUID: 9f2f8ab4-ead5-11e9-9d60-3106f5b1d025

--000e0cd296007a1194047919cedf
Content-Type: text/plain; charset=ISO-8859-1

>  Rc forks a new process for every [non builtin] command it runs. To
> avoid such, use the . command to source the script instead of running
> it.
>
Ok. The thing about forking is clear. Yes, your suggestion of using . would
'solve' the problem of seeing the variables set in the 'a' script (called
from 'b'). However then I would e.g. really have to care about individual
'cd' commands in the 'a' script so as to know where I am after returning
back to the 'b' script. I thought there would be some way to make the 'b'
script reread the environment (i.e. to achieve information passing through
the environment). What is the use of that 'caching' that hinders this way?

 Each process has a current dir. I don't think it is ever shared between
> them.
> -sqweek
>

Ok. I was tired...

Thanks
Ruda

--000e0cd296007a1194047919cedf
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br>
<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">=A0Rc forks a ne=
w process for every [non builtin] command it runs. To<br>
avoid such, use the . command to source the script instead of running<br>
it.<br>
<div class=3D"im"></div></blockquote><div>Ok. The thing about forking is cl=
ear. Yes, your suggestion of using . would &#39;solve&#39; the problem of s=
eeing the variables set in the &#39;a&#39; script (called from &#39;b&#39;)=
. However then I would e.g. really have to care about individual &#39;cd&#3=
9; commands in the &#39;a&#39; script so as to know where I am after return=
ing back to the &#39;b&#39; script. I thought there would be some way to ma=
ke the &#39;b&#39; script reread the environment (i.e. to achieve informati=
on passing through the environment). What is the use of that &#39;caching&#=
39; that hinders this way? =A0<br>

<br>
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex;">=A0Each process has a current dir. I =
don&#39;t think it is ever shared between them.<br>
<font color=3D"#888888">-sqweek<br>
</font></blockquote></div><div><br></div><div>Ok. I was tired...<br></div><=
div><br></div><div>Thanks</div><div>Ruda</div>

--000e0cd296007a1194047919cedf--