Path: utzoo!utgpu!water!watmath!clyde!bellcore!tness7!tness1!sugar!peter From: peter@sugar.uu.net (Peter da Silva) Newsgroups: comp.sys.amiga Subject: Re: Enviroment (was Re: Yea, but can an Amiga Shell do this....) Message-ID: <2512@sugar.uu.net> Date: 20 Aug 88 14:02:19 GMT References: <8808192105.AA16960@cory.Berkeley.EDU> Organization: Sugar Land Unix - Houston, TX Lines: 35 In article <8808192105.AA16960@cory.Berkeley.EDU>, dillon@CORY.BERKELEY.EDU (Matt Dillon) writes: > :In article <1877@iscuva.ISCS.COM>, ricks@iscuva.ISCS.COM (Rick Schaeffer) [ talks about a process' environment ] [ I said: ] > :The problem is that for CLI programs there isn't a clear definition of what [ the environment is... ] > 1.3 has got enviroment variables. Guess how they're implemented! This is a classic example of how the UNIX terminology confuses things. What I mean, and what I thought Rick Schaeffer meant, is the whole environment of the shell: Current directory. Open files. Priority. Path. And so on... Environment variables, on the Amiga, aren't even part of the environment. They're global to the system as a whole... which causes even more confusion. As an aside, I like the way Commodore has set up the global system variables, but I think that they should really be stuck in CLIP:, so they can be flushed to disk when memory gets tight. What, you mean there isn't a CLIP:??? Before doing a real ENV:, do a CLIP: device and just map ENV: to it. What's a CLIP:? Simple... it's a device interface to the clipboards... -- Peter da Silva `-_-' peter@sugar.uu.net Have you hugged U your wolf today?