Shell Programming and Scripting

That's what you asked for. If you don't want it loaded, you may have to live with the limited prompt. I have one good idea: Tell me what your perl script is so we can get rid of the perl and turn it into a csh one that can be sourced without creating a new shell.

I have already did a setting of 'setenv LS_BA_STEM LSB_SGE' in .cshrc.

I must modify LS_BA_STEM value for some reason in the perl script in the below and make new value take effect in current Terminal and also the Terminal prompt must keep raw style just as ctm:/home/wch>

I am using the perl script provided by you.

By the way, my requirement is that all these operation should be did in perl script not allowing source a cshell script manually again in terminal after run over 1.pl.

I am very sorry that my perl script is very long and it cannot be converted to cshell at all. The transform is unimaginable.
I think that the perl script transform to cshell script is not a good idea.

You can did a test for following script.

Code:

#!/usr/bin/perl

$ENV{MYVAR}="asdf";

my $shell=shift;
if($shell) {
        exec $shell, @ARGV;
}
else
{
        exec "bash", "-sh";
}

Thanks.

I did indeed test it, before I posted it. There is nothing wrong with the perl program. Nothing can stop csh from setting its own variables except csh.

Perhaps you could modify your tcshrc to set the environment only when not already set instead. That way, you can reload your tcshrc and get your fancy prompt without overwriting the important environment variable.

Code:

if($ENVVAR == "") then
        setenv ENVVAR "whatever"
endif