Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!uw-beaver!tektronix!tekig!phils
From: phils@tekig.TEK.COM (Phil Staub)
Newsgroups: comp.sys.amiga
Subject: Re: Running Manx C under Drew Shell
Message-ID: <631@tekig.TEK.COM>
Date: Sun, 6-Dec-87 19:15:18 EST
Article-I.D.: tekig.631
Posted: Sun Dec  6 19:15:18 1987
Date-Received: Sat, 12-Dec-87 12:42:17 EST
References: <528@sunspot.UUCP> <5500005@hpfcdc.HP.COM>
Reply-To: phils@tekig.UUCP (Phil Staub)
Organization: Tektronix, Inc., Beaverton, OR.
Lines: 25

In article <5500005@hpfcdc.HP.COM> stroyan@hpfcdc.HP.COM (Mike Stroyan) writes:
[ stuff deleted about problems w/ Manx cc and Steve Drew's shell ]

>This is a shot in the dark, but perhaps you are having trouble with
>the shell's set command vs. the Manx set command.  You need to set
                                                    ^^^^^^^^^^^^^^^
>the Manx environment variables with "Set" or before starting shell,
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>so that the set program runs rather than the shell intrinsic which
>sets shell variables that cc can't see.
>
>Mike Stroyan, hpfcla!stroyan


Nope. You can still access any disk resident command whose name happens to
conflict with a shell built-in by typing the name of the command with one or
more capital letters. Thus "set" gets you the shell's set, and "Set" gets
you the AmigaDOS version.

  .Phil
-- 
------------------------------------------------------------------------------
Phil Staub                     "I do NOT approve. I merely said I UNDERSTAND."
tektronix!tekigm2!phils                                              - Spock
phils@tekigm2.TEK.COM