From: jp AT nuancecom DOT com (JP Shipherd)
Subject: bash won't hand off to tcsh
4 Mar 1997 01:49:41 -0800
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <3.0.32.19970303161403.00cd5e40.cygnus.gnu-win32@awesome.nuance.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Sender: jp AT awesome DOT nuance DOT com
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Original-To: gnu-win32 AT cygnus DOT com
Original-Sender: owner-gnu-win32 AT cygnus DOT com

Hi,

  I've got lots of csh shell scripts.  To my joy today I found a copy of
tcsh.exe which I put in /bin.  (I even copied it to csh.exe at one point).

  However if I run a script like setfoo:

#!/bin/csh -f
setenv foo FooIsSet
echo $foo
exit(0)

  from a bash shell, bash insists on trying to interpret the script itself
instead of handing it off to the command interpreter I'm specifying on the
first line.  As you might imagine it doesn't deal with setenv too well.

  (The script runs fine if I exec tcsh first and then run it).

  Am I missing something simple?

  Does bash not allow other shells to muscle in on it's turf?

Thanks for any help.  I don't relish rewriting over 200 scripts.

--jp
-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".