home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Education Sampler 1992 [NeXTSTEP]
/
Education_1992_Sampler.iso
/
NeXT
/
Misc
/
HigherEducationMailbox.mbox
/
Archives_provide_val_.attach
/
May_91
/
workspace.660
< prev
next >
Wrap
Text File
|
1991-05-21
|
1KB
|
41 lines
{\rtf0\ansi{\fonttbl\f0\fnil Times-Roman;\f1\fmodern Courier;\f2\fswiss Helvetica;}
\paperw11040
\paperh9800
\margl120
\margr1000
{\colortbl\red0\green0\blue0;}
\pard\tx960\tx1920\tx2880\tx3840\tx4800\tx5760\tx6720\tx7680\tx8640\tx9600\f0\b0\i0\ul0\fs28 running shell scripts from the 2.0 Workspace\
\
Q: When I double-click on a shell script in the 2.0 Workspace, a shell window appears, but then immediately displays a “
\fc0 [process terminated]” message. My script never executes. It worked fine under 1.0 — what's wrong?\
\
A: There's a good chance that your shell script expects to be executed by
\f1\fs24 csh
\f0\fs28 . When you double-clicked on a shell script in the 1.0 Workspace, it invoked the
\f1\fs24 Terminal
\f0\fs28 application which would use whatever shell you specified as part of your
\f1\fs24 UNIX
\f0\fs28 login information to execute your script. In 2.0, the Workspace invokes one of its lightweight shells and uses
\f1\fs24 exec
\f0\fs28 to execute your shell script.
\f1\fs24 exec
\f0\fs28 won't invoke
\f1\fs24 csh
\f0\fs28 by default, so you need to do this explicitly by making the following the first line of the shell script file:\
\
\f1\fs24 #! /bin/csh -f\
\f0\fs28 \
Please refer to NeXTanswer
\f1\fs24 shell.448
\f0\fs28 for more information on
\f1\fs24 csh
\f0\fs28 and shell scripts.\
\
Verified for 2.0\
\
QA660\
\