Hi, Dave.

Just wondering -
What do you do with it?
It seems like I should be the classical user (always having open one
squeak and one terminal).

"David T. Lewis" <lewis at mail.msen.com> wrote:
> 
> --tKW2IUtsqtDRztdT
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> 
> CommandWindow 1.1
> Previous released version: 1.0
> Requires OSProcess 2.2
> 
> A Unix style command shell written in Smalltalk, with a Morphic terminal
> window (tty only, no termcap stuff). This is beginning to be a rather useful
> utility for people who use Squeak on Unix or Linux. In principle this could
> be used on non-Unix systems, although the ports of OSProcess to other
> platforms have yet to be written.
> 
> - Dave
> 
> Changes since version 1.0:
> 
> 1) Added an 'edit' file editor command to CommandShell as a shell builtin.
> This makes it convenient to edit files from a CommandShell without resorting
> to an external editor (vi or emacs), and also allows command output
> to be easily displayed in an editor in Smalltalk. Note: There was a
> version 1.0.1 patch release posted. This version replaces the 1.0.1
> patch and contains a nicer implementation of the 'edit' builtin.
> Try 'edit /etc/hosts' to edit a file, or 'who | edit' and
> 'cat /proc/version | edit' to pipe Unix commands into Smalltalk text editors.
> 
> 2) Added an 'inspect' shell builtin to allow command output or file
> contents to be easily piped to a Smalltalk inspector. Try
> 'cat /etc/hosts | inspect' or 'inspect < /etc/hosts'.
> 
> 3) Moved class UnixCommand out of OSProcess and into CommandWindow.
> 
> 4) Fixed semantics of argument name expansion in UnixCommand.
> Problem: Argument expansion in a CommandShell resulted in arguments
> being expanded to fully qualified file names relative to the file system
> root, even if the specified file was in the current working directory.
> The correct expansion in this case would be just the file name, not
> the fully qualified path.
> 
>