[Coco] Re: Path command wasRe: OS-9 LVL II

[Robert Gault]

Here is the relevant passage.

"USER STARTUP FILE EXECUTION
---------------------------

The reserved word 'S.T.A.R.T.U.P' will cause the shell to attempt 
running a file called 'startup' in the CURRENT directory. This is very 
useful when  running Tsmon/Login and you are changing the users working 
directory. If the  users directory is changed and then the program 
forked is 'shell s.t.a.r.t.u.p' the shell will try to run a startup file 
in the new directory and then remain active. If no startup file is 
present, no error is returned."

This does not seem to relate to the current question. Willard, have you 
tested this either with or without Tsmon/Login to see if it works for 
gaining multiple command directories?

Willard Goosey wrote:
>>Date: Sat, 19 Feb 2005 08:29:08 -0500
>>From: Robert Gault <robert.gault at worldnet.att.net>
> 
> 
> Um, we had this discussion a few months ago.  I'll just reprise the
> highlights....
> 
> 
>>I had just reported what was contained in the shellplus doc. After some 
>>testing, I have found when the path= command is entered from the 
>>keyboard, the paths are inherited by any new shell. If the command is 
>>placed in a script file or Startup, the paths won't stick unless the 
>>last line of the script is   i=/1   .
> 
> 
> OK, the shell that runs the STARTUP script is started by cc3go (or
> sysgo) and then that shell goes away.  The /term shell is not a child
> of it, so it doesn't inherit the shell+ internal vars.
> 
> However, on startup a shell+ shell looks for a file called
> s.t.a.r.t.u.p (or something like this)  This file is interpeted by the
> shell, rather than a child shell like a regular script.  You can set
> variables like path and prompt in it.
> 
> The exact details are left for someone to read the shell+ docs for.
> 
> Willard
>