frazier@oahu.cs.ucla.edu (Greg Frazier) (07/10/90)
Hello. I have a few questions about our A3000 and it's
documentation. First, this is our first Amiga, so we
are trying to get teh hang of this OS. First, why don't
any of the examples in the documentation work? For example,
l> date > foo
works, but
l> echo < foo
does not. No error msg, but nothing gets printed out.
As for
l> copy foo >> bar
I get the error msg that bar has to be a directory. How
can redirection be not working in this fashion? I mean,
this isn't subtle, and those are all examples straight out
of the manual.
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?
Any comments on the above, or on the documentation/OS in
general, would be appreciated (particularly constructive
ones :-).
--
"They thought to use and shame me but I win out by nature, because a true
freak cannot be made. A true freak must be born." K. Dunn, _Geek_Love_
Greg Frazier frazier@CS.UCLA.EDU !{ucbvax,rutgers}!ucla-cs!fraziermartin@cbmvax.commodore.com (Martin Hunt) (07/11/90)
In article <36868@shemp.CS.UCLA.EDU> frazier@oahu.cs.ucla.edu (Greg Frazier) writes: >Hello. I have a few questions about our A3000 and it's >documentation. First, this is our first Amiga, so we >are trying to get teh hang of this OS. First, why don't >any of the examples in the documentation work? For example, > >l> date > foo >works, but >l> echo < foo > >does not. No error msg, but nothing gets printed out. >As for >l> copy foo >> bar >I get the error msg that bar has to be a directory. How >can redirection be not working in this fashion? I mean, >this isn't subtle, and those are all examples straight out >of the manual. Unfortunately, the manual is set in a proportional font so you can't see the spaces. There should be no spaces between the redirection operators and the filename. For example, date >foo Echo <foo doesn't seem to work correctly >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 "". -- Martin Hunt martin@cbmvax.commodore.com Commodore-Amiga Engineering {uunet|pyramid|rutgers}!cbmvax!martin
lockhart@cbmvax.commodore.com (John W. Lockhart - Product Assurance) (07/11/90)
In article <36868@shemp.CS.UCLA.EDU>, frazier@oahu.cs.ucla.edu (Greg Frazier) writes: >l> date > foo >works, but >l> echo < foo > >does not. No error msg, but nothing gets printed out. True. But try date >env:foo echo "$foo" >l> copy foo >> bar >I get the error msg that bar has to be a directory. How >can redirection be not working in this fashion? I mean, >this isn't subtle, and those are all examples straight out >of the manual. To append foo to bar, use type >>bar foo instead. >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. Try typing 'resident' at a shell prompt to see the list of built-in Shell commands. UNSETENV is there in place of 'setenv remove'. >Greg Frazier frazier@CS.UCLA.EDU !{ucbvax,rutgers}!ucla-cs!frazier -- John ------------------------------------------------------------------------------ John Lockhart, lockhart@cbmvax.commodore.com; BIX: jlockhart Systems Evaluation Group, Product Assurance Dept., Commodore Working for, but not speaking for, Commodore.
jjszucs@cbmvax.commodore.com (John J. Szucs) (07/11/90)
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