Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!elroy.jpl.nasa.gov!decwrl!adobe!heaven!heaven.woodside.ca.us
From: glenn@heaven.woodside.ca.us (Glenn Reid)
Newsgroups: comp.sys.next
Subject: Re: what are your UNIX-NeXTStep conflicts (was Re: UI idea)
Message-ID: <519@heaven.woodside.ca.us>
Date: 4 Jun 91 08:03:22 GMT
References: <1991Jun3.050426.28427@math.ucla.edu>
Sender: glenn@heaven.woodside.ca.us
Lines: 33

Barry Merriman writes

> (6) looking/getting inside of an <Appname>.app directory,
>     mailboxes, and other directories that the browser can't 
>     see inside of (I hate when that happens!)

Use command-O (capital O) to get inside these packages.  It's called
"Open as Folder" in the menu.

> (8) compiling

You can sort of run "Make" from interface builder, but I'll agree that
it's less than perfect.

> (9) doing ``ls -a'' to see files starting with a ``.'',
>     or to look in UNIX directories like /etc, etc.
>      (I know the UNIX Expert setting in Preferences toggles this,
>       but its a pain to have to use Preferences to change it)

Just start typing the path (with . or /etc or whatever) and the "Finder"
pops up to help you complete the path.  It also jumps into UNIX Expert
mode if you've typed a leading . or a path that is hidden.

> (10) running shell scripts

Just double-click them, unless they require arguments.

All in all, you're right about the deficiencies, and I agree with you.

--
 Glenn Reid				RightBrain Software
 glenn@heaven.woodside.ca.us		NeXT/PostScript developers
 ..{adobe,next}!heaven!glenn		415-326-2974 (NeXTfax 326-2977)