Xref: utzoo comp.sys.amiga:14709 comp.sys.misc:1189
Path: utzoo!mnetor!uunet!husc6!bloom-beacon!mit-eddie!ll-xn!ames!pasteur!ucbvax!hplabs!sdcrdcf!trwrb!cadovax!keithd
From: keithd@cadovax.UUCP (Keith Doyle)
Newsgroups: comp.sys.amiga,comp.sys.misc
Subject: Re: Cleaner PopCLI path(?)
Message-ID: <1943@cadovax.UUCP>
Date: 18 Feb 88 21:49:01 GMT
References: <10373@ut-sally.UUCP>
Reply-To: keithd@cadovax.UUCP (Keith Doyle)
Organization: Contel Business Systems, Torrance, CA
Lines: 42

In article <10373@ut-sally.UUCP> bryan@mothra.cs.utexas.edu writes:
>
>	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.  

We just ran into a related problem recently.

Try this:

main()
{
	Execute("cd",0L,0L);
}

No matter where you run this program from, the result is *always* DF0:.
Even if everything has been reassigned elsewhere and there is not even
a disk in drive 0.

We wondered where it was getting the DF0: from, and found that it is
hard coded in the CD program.  It is also hard coded in the Assign program
and probably a few others.

What we wanted to do, was to have a program that did a:

	Execute("Assign foo: stuff",0L,0L);

such that no matter where the program was, no matter how deeply nested
into hard-disk subdirectories it might be, it will always find "stuff"
relative to the current directory as percieved by the "Execute"ing program.

We discovered:   You can't get there from here.

As far as I know, there is no way to get an Executed command to use
the current programs current directory as its current directory.  Or
anything but DF0: for that matter.

I'd like to be proven wrong.

Keith Doyle
#  {ucbvax,decvax}!trwrb!cadovax!keithd  Contel Business Systems 213-323-8170