comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » IDL and UNIX setenv
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: IDL and UNIX setenv [message #25511 is a reply to message #25428] Tue, 19 June 2001 00:25 Go to previous messageGo to previous message
Randall Skelton is currently offline  Randall Skelton
Messages: 169
Registered: October 2000
Senior Member
> I think you might need to add the path to your default .profile/.login/.cshrc/.whatever
> (which I am assuming you're not doing - I really can't tell from "I tried to append the
> /usr1/guest/bin/ directory to my UNIX path before starting an IDL session")
>
> I *think* when you use SPAWN, the subsequent shell in which the SPAWN command argument is
> executed is *not* the one you started IDL in and therefore has no knowledge of what you
> may have explicitly defined. The same sort of thing happens in make files in Unix.

Paulv is indeed correct here. Using spawn will start a *new* process
(with a unique pid) and therefore it does not interact or have any
knowledge of the shell or environment variables you had when you started
IDL. You might be able to pass the IDL '!PATH' variable in a string when
you use spawn, but you'll need to be careful this concatenated string of
path + command doesn't get too long. Modifying your .login/.cshrc to
append the required path is the cleanest option by far.
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: regression with poisson models
Next Topic: 10 bit packed as 8 bit unpacking

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 19:36:39 PDT 2025

Total time taken to generate the page: 0.00373 seconds