If you're in a csh shell (or most other shells), then yes, entering source sge_sigma.csh at the command line will cause the contents of that file to be interpreted and take effect in the current shell.
bannor:~/work/perl/monks$ csh
bannor:~/work/perl/monks> cat test.csh
setenv MYTEST "This is a test."
bannor:~/work/perl/monks> echo $MYTEST
MYTEST: Undefined variable.
bannor:~/work/perl/monks> source test.csh
bannor:~/work/perl/monks> echo $MYTEST
This is a test.
You can't do this from within a Perl script, because it's a sub-process of the shell, so it can't change its parent's environment. To put it another way, you can change environment variables within a Perl script by use of the %ENV hash, and those will be inherited by any child processes that your Perl script spawns, but they can't go "upstream" to the parent process.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|