Path: utzoo!attcan!uunet!husc6!rutgers!ucsd!ucsdhub!loral!dml From: dml@loral.UUCP (Dave Lewis) Newsgroups: comp.sys.amiga Subject: Re: ENV: variables (and Arp Set strangeness) Keywords: Shell Message-ID: <1835@loral.UUCP> Date: 7 Sep 88 15:47:44 GMT References: <8809070041.AA11163@cory.Berkeley.EDU> Reply-To: dml@loral.UUCP (Dave Lewis) Followup-To: comp.sys.amiga Distribution: na Organization: Loral Instrumentation, San Diego Lines: 33 In article <8809070041.AA11163@cory.Berkeley.EDU> dillon@CORY.BERKELEY.EDU (Matt Dillon) writes: > >:There has been recent discussion of the ENV: stuff in 1.3 ... > And if you *really* want private enviroment variables simply make > a sub-directory in ENV: ... but the program(s) would have to support it. > -Matt But Matt, you already GOT that! (you DO use your Shell, don't you?) Use the Arp C:Set command for global variables that are accessable to any process, and the Shell's built-in "set" for privates. Admittedly, these are not part of the "standard" AmigaOS, but they are both public domain. This system works fine for me on my Aztec disk - the compiler's INCLUDE, CCTEMP and CLIB variables are global and each shell gets to create its own _path, _prompt and so on. I'm going to add support for the Arp Set variables to the Shell (along with all the other stuff I'm adding). I'm making so many changes that this thing could qualify for a new release instead of just diff's. BTW, I did figure out the semicolon business with Arp's Set: 1> Set "INCLUDE=path1;path2;path3" "CLIB=path4;path5;path6;;" works just fine. Advice: don't screw around with new stuff in the middle of the night. It produces symptoms remarkably similar to a hangover. Still haven't figured out how to use Resident and ARun with programs that don't open their own windows, though. I WANT to make the Shell Resident. -- Dave Lewis Loral Instrumentation San Diego (619) 282-3341 ihnp4 --\ bang --\ kontron -\ hp-sdd --\ calmasd ->-> crash ->--> loral!dml sdcrdcf -->--------> sdcsvax -/ (uucp)