Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!purdue!decwrl!ucbvax!hplabs!hpfcdc!hpldola!hp-lsd!tbc
From: tbc@hp-lsd.HP.COM (Tim Chambers)
Newsgroups: comp.windows.x
Subject: Re: Re^2: Shell in an X-Window
Message-ID: <14330003@hp-lsd.HP.COM>
Date: 3 Aug 89 16:33:32 GMT
References: <18116@paris.ics.uci.edu>
Organization: HP Logic Systems Division - ColoSpgs, CO
Lines: 64

In article dbainbri@ics.uci.edu (David Bainbridge) writes:
> Is it possible to open a shell in an X-window...

I have wanted such a beast, too.  I would like a "command dispatcher" that
opens a window for each command line executed.  Although not exactly what I
want, pam(1), available as a standard command on HP-UX, is an example of such
an alternative to terminal-based shells.  I quote the man page for examples:

          Pam is a program that provides a friendlier, less
          intimidating means of communication between HP-UX and system
          users.  It provides many of the traditional capabilities
          supported by other shell programs, such as executing
          commands as foreground processes (that is, where you must
          wait until one command has been completed before the system
          accepts the next command) or background processes (where the
          command runs in the background while you perform other tasks
          in the foreground).

          ...

          In a windowed system, interactive commands are treated as
          background processes (&) unless a semicolon is present at
          the end of the line.

          Standard Input, Output, and Error Files

             The standard input, output, and error of a command can be
             redirected using the following syntax:

             ...

(This is the feature *I* like about it!)

             # name              [For windowed systems only] Use the
                                 named window as standard input,
                                 output and error for the command.  If
                                 the window doesn't exist, a window is
                                 created.  Specific redirection of I/O
                                 with >, >>, <, |, ^, or ^^ overrides
                                 any redirection specified with "#".


One undesirable feature of pam is that it was designed to run on *either*
a terminal *or* in a windowed environment, so pam itself consumes an xterm
window just like sh(1) or ksh(1) does.  I think David wants a shell that is
independent of xterm for I/O.  I know *I* do.

The following response is the complete man page for pam, in case I've piqued
your curiosity.

A caveat:  The multi-window feature may be broken for HP-UX 6.5.  I liked it
under 6.2, though.  I chose not to complain since it might be pilot error on
my part; *but*, if you are an HP trade customer, try pam as a result of this
posting, and find defects, then COMPLAIN TO YOUR HP SALES REPRESENTATIVE!  (I
hope there aren't negative reactions to this recommendation, but please post a
separate note in comp.sys.hp if you have comments pro or con rather than
drifting here -- HP customer service would be an interesting topic of notes
conversation on its own.)

Disclaimer:  I work on host-based instruction set debugger/simulators of
mainstream microprocessors and am not making this posting as an HP employee
who has a vested interest in pushing the command recommended here.

    - Tim Chambers