Path: utzoo!attcan!uunet!husc6!mailrus!bbn!bbn.com!levin
From: levin@bbn.com (Joel B Levin)
Newsgroups: comp.sys.mac
Subject: Re: Finder proposal: CLI's (long)
Message-ID: <32742@bbn.COM>
Date: 28 Nov 88 16:22:05 GMT
References: <928@dogie.edu> <1679@pur-phy>
Sender: news@bbn.COM
Reply-To: levin@BBN.COM (Joel B Levin)
Distribution: na
Organization: BBN Communications Corporation
Lines: 29

In article <1679@pur-phy> sho@newton.physics.purdue.edu.UUCP (Sho Kuwamoto) writes:
|cd.  Second, MPW doesn't seem to have a path.  I don't use MPW, so I

If you mean in the unix sense of an environment variable used to
identify directories containing commands, yes, it does.

|under the Finder.  I don't feel comfortable with the MPW shell for
|some unknown reason.  I'm probably just not used to it.  One of the
|reasons is that I don't like it is psychological.  On a UNIX machine,
|or egad! an MS-DOS machine, I feel like I am communicating with the
|machine at a very low level.  assembly:pascal::cli:windows.  But under
|MPW, I feel like I'm running a fancy text-editor which can interpret
|my commands and pass them on to the Finder.  Don't get me wrong, the
|MPW shell is very powerful.  It's just this feeling I have that I'm
|not at the heart of the machine.

Mostly you are as much at the heart of the machine with MPW as with
the finder; you just don't see the picture that finder presents.
There are commands to move, delete and copy files, etc.; when MPW
launches (not under multifinder) you are returned there; etc.  Finder
and MPW Shell are both applications to the OS; neither is really
closer in the sense you mean, I think.

|-Sho

	/JBL

UUCP:     {backbone}!bbn!levin		POTS: (617) 873-3463
INTERNET: levin@bbn.com