🚀 go-pugleaf

In article <1ictqqINNk4a@tamsun.tamu.edu> vamsee@abgen.tamu.edu (Vamsee Lakamsani) writes:
>%xwsh -e rlogin <any-host>
>
>The above command works on this SGI (Indigo 4.0.5A). But,
>
>%xwsh -e /bin/ls
>%xwsh -e cd /usr/people/vamsee/junk
>%xwsh -e chdir /usr/people/vamsee/junk
>%xwsh -e cd /usr/people/vamsee/junk; vi <somefile>
>
>don't work. The man page says:
>
>" The -e option will pass all trailing arguments to xwsh , to be
>   executed as a command line."
>
>What's the difference ? Why does rlogin work and the others don't?
>There must be a way to do this simple thing. Any help is appreciated.
>
>Vamsee
>
-----------------------------------------------
Response:
xwsh terminates immediately after the commands terminate.
rlogin doesn't terminate, therefore the window hangs around.

SGI provided a command file with buttonfly that I have used in the past.
It contains the following:

#! /bin/csh -f
$*
echo -n "<ENTER to continue>"
set foo $<

I called this "mywsh".  It is used as follows:

xwsh -e mywsh ls

It executes the command then waits for you to terminate it after it completes.

By the way, 
    %xwsh -e cd /usr/people/vamsee/junk; vi <somefile>
is the same as:
    %xwsh -e cd /usr/people/vamsee/junk
    % vi <somefile>
The ";" signifies the end of the xwsh command.

-- 
Jim Moore                       Hughes Training Inc.
Phone: (612) 572-7721           5301 East River Road
Fax:   (612) 572-7732           Mpls, Mn. 55421-1024
Email: jfm@asf.com              USA