comp.lang.idl-pvwave archive: archive » Re: @make vs command line for creating .sav files.

Home » Public Forums » archive » Re: @make vs command line for creating .sav files.

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: @make vs command line for creating .sav files. [message #50256]

Thu, 21 September 2006 12:46

savoie
Messages: 68
Registered: September 1996

Member

David Fanning wrote:
> David Fanning writes:
>
>>
>> I've tried running my startup file directly after the .RESET
>> and that doesn't help either. Something weird is going on
>> here. I can't even set the !PATH and get it to work!
>>
>> Here is my file fake_save.pro:
>>
>> .reset_session
>> !path = !path + "c:\RSI\DAVID\TEST"
>> !path = expand_path( !path )
>> .compile fake_needs
>> resolve_all

Aha. This might do what I want. ... Yup. What I really wanted was to
be able to control the path with an environmental variable and I can.

Thanks everyone for the help. I don't think I would have thought of
rebuilding the path in the batch file.

--
Matthew Savoie - Scientific Programmer
National Snow and Ice Data Center
(303) 735-0785 http://nsidc.org

Report message to a moderator

[Message index]

Re: @make vs command line for creating .sav files.

By: savoie on Thu, 21 September 2006 12:46

Previous Topic:	Re: @make vs command line for creating .sav files.
Next Topic:	WHERE functiom

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Fri Oct 10 15:31:42 PDT 2025

Total time taken to generate the page: 1.67807 seconds