home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.sgi.misc:180 comp.sys.sgi.apps:34 comp.sys.sgi:18544
- Newsgroups: comp.sys.sgi.misc,comp.sys.sgi.apps,comp.sys.sgi
- Path: sparky!uunet!cs.utexas.edu!sun-barr!ames!agate!dog.ee.lbl.gov!hellgate.utah.edu!lanl!mpx2.lampf.lanl.gov!odonnell
- From: odonnell@mpx2.lampf.lanl.gov (John M. O'Donnell)
- Subject: Re: strange problem with command execution at xwsh startup
- Message-ID: <6JAN199321283309@mpx2.lampf.lanl.gov>
- News-Software: VAX/VMS VNEWS 1.41
- Sender: news@newshost.lanl.gov
- Organization: LAMPF Data Analysis Center, Los Alamos, New Mexico
- References: <1ictqqINNk4a@tamsun.tamu.edu> <1993Jan6.144904.4811@asf.com>
- Date: Thu, 7 Jan 1993 04:28:00 GMT
- Lines: 20
-
- In article <1993Jan6.144904.4811@asf.com>, jfm@asf.com (Jim Moore) writes...
- >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.
- >
- xwsh -h saves a lot of messing around with extra files like mywsh
-