Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uwm.edu!cs.utexas.edu!rutgers!bpa!cbmvax!jjszucs From: jjszucs@cbmvax.commodore.com (John J. Szucs) Newsgroups: comp.sys.amiga Subject: Re: What's the deal with the A3000+documentation Message-ID: <13133@cbmvax.commodore.com> Date: 10 Jul 90 18:32:45 GMT References: <36868@shemp.CS.UCLA.EDU> <13131@cbmvax.commodore.com> Reply-To: jjszucs@cbmvax (John J. Szucs) Organization: Commodore, West Chester, PA Lines: 42 In article <13131@cbmvax.commodore.com> martin@cbmvax (Martin Hunt) writes: >In article <36868@shemp.CS.UCLA.EDU> frazier@oahu.cs.ucla.edu (Greg Frazier) writes: [text deleted] >>And how about setenv? Supposedly, given an environment >>variable (foo), I can remove it via >>l> setenv foo remove >>but what I end up with is having "remove" assigned to foo. >>Is this somebody's idea of a joke? > >This appears to be a bug. Try setenv foo "". The functionality of the REMOVE option of SetEnv has been moved to the new UnSetEnv command. For example, to set the environment variable foo to "bar", display the value, and remove the variable: 1.SYS:> setenv foo bar 1.SYS:> echo $foo bar 1.SYS:> unsetenv foo 1.SYS:> echo $foo $foo (indicates environment variable foo is not set) The documentation is in error by indicating the REMOVE option for SetEnv and by not documenting UnSetEnv. > > >-- >Martin Hunt martin@cbmvax.commodore.com >Commodore-Amiga Engineering {uunet|pyramid|rutgers}!cbmvax!martin ================================================================================ || John J. Szucs || The opinions expressed are my own and || || Systems Evaluation Group || in no way represent the opinions or || || Product Assurance Department || policies of Commodore Technology, Inc. || || Commodore Technology, Inc. || or any associated entity. || ================================================================================ ...{rutgers|uunet|pyramid}!cbmvax!jjszucs jjszucs@cbmvax.commodore.com