| IDL_STARTUP trouble and .kshrc [message #33675] |
Sun, 19 January 2003 12:19  |
dave-keller
Messages: 1
Registered: January 2003
|
Junior Member |
|
|
I want to use an alternate 'IDL_STARTUP' file when running IDL from a
scheduled ('cron') job. I used to do this all the time on Sun and HP
workstations. But now on an IBM workstation, it seems that IDL takes
the IDL_STARTUP variable STRICTLY FROM MY .kshrc, as if IDL reads the
.kshrc file!
From a ksh on an IBM:
(assume I have files 'mystartup.pro' and 'mystartup_v2.pro')
% export IDL_STARTUP='~/mystartup_v2.pro'
% idl
'This is the old startup program' (message in the mystartup.pro
file)
IDL> print,getenv('IDL_STARTUP')
mystartup.pro
IDL> exit
echo $IDL_STARTUP
'mystartup_v2.pro'
What is also odd is that I can modify my .kshrc file, AND NOT EVEN
'EXECUTE' IT, and IDL will use THE IDL_STARTUP VARIABLE IN THE .kshrc
FILE!
.kshrc:
export IDL_STARTUP='mystartup.pro' (IDL WILL USE mystartup.pro)
export IDL_STARTUP='mystartup_v2.pro' (IDL WILL USE mystartup_v2.pro)
I want to specify, 'dynamically', which IDL_STARTUP file to use, on
this IBM system. But IDL seems to 'read' my .kshrc file, and use
whatever the environmental variable IDL_STARTUP is, from there. IDL
reads my .kshrc whether or not I 'execute' it, all I have to do is
modify the .kshrc with an editor, and IDL will follow. This is not
what I expect, I expect IDL to honor my IDL_STARTUP variable.
I think ksh is the predominant shell on our system, so I'd prefer
that, but it may be that using 'c' shell is the solution?
Heeeeelp?
-- Dave --
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
