Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!decwrl!mcnc!wolves!deepthot!Jay From: Jay@deepthot.UUCP (Jay Denebeim) Newsgroups: comp.sys.amiga.programmer Subject: Re: CLI path Message-ID: Date: 31 Jan 91 05:52:15 GMT References: <18122@cbmvax.commodore.com> Organization: The Software Distillery Lines: 34 In article <18122@cbmvax.commodore.com> andy@cbmvax.commodore.com (Andy Finkel) writes: >Then there's workbench. When Workbench fires up via LoadWB, it snapshots >the paths in effect in that shell. > >This is the paths that get copied when starting a shell from workbench, ie >from the CLI icon, or from tools like PopCLI. > Actually, I think the path PopCLI gets is the one that was in effect when PopCLI was run, not the LoadWB one. Makes sense, each process inherits its parent's attributes. Generally this is the same thing of course because startup sequences would have a bunch of path assignments etc, then the background processes such as PopCLI and LoadWB get fired off. > andy >-- >andy finkel {uunet|rutgers|amiga}!cbmvax!andy >Commodore-Amiga, Inc. > >"God was able to create the world in only seven days because there > was no installed base to consider." ^- love that quote. > >Any expressed opinions are mine; but feel free to share. >I disclaim all responsibilities, all shapes, all sizes, all colors. -- |_o_o|\\ |. o.| || The Jay Denebeim | . | || Software | o | || Distillery | |// Address: mcnc!wolves!deepthot ====== BBS:(919)-460-7430 VOICE:(919)-460-6934