> 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
