Xref: utzoo comp.sys.amiga:14374 comp.sys.misc:1143
Path: utzoo!utgpu!water!watmath!clyde!rutgers!im4u!ut-sally!mothra!bryan
From: bryan@mothra.cs.utexas.edu (Bryan Bayerdorffer)
Newsgroups: comp.sys.amiga,comp.sys.misc
Subject: Cleaner PopCLI path(?)
Message-ID: <10373@ut-sally.UUCP>
Date: 16 Feb 88 06:04:28 GMT
Sender: news@ut-sally.UUCP
Reply-To: bryan@mothra.cs.utexas.edu
Organization: Spam Detection & Removal Squad, Austin, TX
Lines: 22
Spam-Content: Tolerable


	Funny how it just takes years to notice some things.  Although I've had
my hard disk for a while now and my command search path has grown accordingly,
I only recently noticed that the CLI launched by popCLI doesn't inherit the
'right' path information.  Since each CLI has its own path, I surmise that the 
CLI launched from the workbench icon gets its path from the CLI in which LoadWB
was executed.  Since that CLI may no longer be around, the workbench must
presumably save the path somewhere.  PopCLI (III), however, passes the minimal
path to its CLIs.  I've been getting around this problem by using
	popcli newcli ... from s:initcli
where s:initcli rebuilds the path (and starts Matt's/Steve's shell, 
of course :-)).  The question is, how to make popCLI remember the path of its
parent CLI, and pass this to its 'children.'  How does one pass environments
around in AmigaDOS in general?  Can you tell that, in what little time I have
for programming, I avoid AmigaDOS like a Botulent can of Spam? 8-}
 ______________________________________________________________________________
/_____/_____/_____/_____/_____/_____/_____/_____/_____/_____/_____/_____/_____/
|_____|_____|_____|_____|_____|_____|_____|_____|_____|_____|_____|_____|_____|
_No dark sarcasm in the classroom|_____|_____|_____|_____|_____|_____|_____|___
|____Teachers leave the kids alone__|_____|_____|bryan@mothra.cs.utexas.edu___|
___|_____|_____|_____|___{ihnp4,seismo,...}!ut-sally!mothra.cs.utexas.edu!bryan
|_____|_____|_____|_____|_____|_____|_____|_____|_____|_____|_____|_____|_____|