csj <[EMAIL PROTECTED]> writes:
> I tend to write scripts which are tcsh-compatible. So
> "#!/bin/tcsh". But its somewhat a waste of effort to write one
> set of scripts for bash and another for tcsh. My main problem is
> handling the variables. Is there a shell-portable way to specify
> varia
On Wed, Nov 12, 2003 at 09:24:04AM +0800, csj wrote:
> I tend to write scripts which are tcsh-compatible. So
> "#!/bin/tcsh".
Wow. You're mad. Sorry :) The C shell is too broken for serious
scripting.
> But its somewhat a waste of effort to write one set of scripts for
> bash and another for tcs
On Mon, 10 Nov 2003 23:18:56 -0700,
Bob Proulx wrote:
>
> csj wrote:
> > Is there a way to write portable shell scripts. In
> > particular, I've problems with built-ins setenv (tcsh) and
> > export (bash). How do I define variables in tcsh and have
> > them
csj wrote:
> Is there a way to write portable shell scripts. In particular,
> I've problems with built-ins setenv (tcsh) and export (bash).
> How do I define variables in tcsh and have them usable in bash
> too?
Your best option is "#!/bin/sh" at the top of all of
On Mon, Nov 10, 2003 at 07:15:56AM +0800, csj wrote:
> Is there a way to write portable shell scripts. In particular,
> I've problems with built-ins setenv (tcsh) and export (bash).
> How do I define variables in tcsh and have them usable in bash
> too?
I don't believe
Is there a way to write portable shell scripts. In particular,
I've problems with built-ins setenv (tcsh) and export (bash).
How do I define variables in tcsh and have them usable in bash
too?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". T
6 matches
Mail list logo
