| Re: Setting the IDL Path [message #72783] |
Wed, 06 October 2010 07:01 |
Jeremy Bailin
Messages: 618
Registered: April 2008
|
Senior Member |
|
|
On Oct 5, 2:02 pm, Paulo Penteado <pp.pente...@gmail.com> wrote:
> On Oct 5, 8:51 am, Jeremy Bailin <astroco...@gmail.com> wrote:
>
>> Incidentally, I can relate from experience that when you have a
>> gazillion variables you want to put in a save file, SAVE, /ALL is not
>> the way to go. Since it also saves !PATH... and if you then try to
>> restore that file on a different system where things are located in
>> different places, you can get yourself very very confused!
>
> IDL_Savefile objects and Craig Markwardt's cmsvlib (http://www.physics.wisc.edu/~craigm/idl/cmsave.html) can help with that,
> allowing to query the file and choose, pack or rename the variables to
> restore.
Good point! Thanks for reminding me that IDL_Savefile existed - I
think I'm going to end up spending this morning cleaning the system
variables out of my old save files...
-Jeremy.
|
|
|
|
| Re: Setting the IDL Path [message #72793 is a reply to message #72783] |
Tue, 05 October 2010 11:02  |
penteado
Messages: 866
Registered: February 2018
|
Senior Member
Administrator |
|
|
On Oct 5, 8:51 am, Jeremy Bailin <astroco...@gmail.com> wrote:
> Incidentally, I can relate from experience that when you have a
> gazillion variables you want to put in a save file, SAVE, /ALL is not
> the way to go. Since it also saves !PATH... and if you then try to
> restore that file on a different system where things are located in
> different places, you can get yourself very very confused!
IDL_Savefile objects and Craig Markwardt's cmsvlib (http://
www.physics.wisc.edu/~craigm/idl/cmsave.html) can help with that,
allowing to query the file and choose, pack or rename the variables to
restore.
|
|
|
|
| Re: Setting the IDL Path [message #72805 is a reply to message #72793] |
Tue, 05 October 2010 04:51 |
Jeremy Bailin
Messages: 618
Registered: April 2008
|
Senior Member |
|
|
On Oct 4, 5:13 pm, David Fanning <n...@dfanning.com> wrote:
> Mark Piper writes:
>> Check! It's now on the list. This would help me, too, because I've
>> been confused by the many different ways to set path, as well as the
>> precedence of these different ways. Maybe we could discuss what
>> particular topics should go into this webinar?
>
> I have a bad feeling there is not going to be
> One Right Way. For example, I *never* let IDL
> anywhere near my !PATH. I want to manage it
> completely myself, so I know what is what.
>
> Dick Jackson, who is as good an IDL programmer
> as anyone I know, tells me he *always* lets
> IDL manage his !PATH. Yikes!!
>
> If we assume that is the yin and the yang of it, I
> wonder where everyone else falls out?
>
> Personally, if I am using a Workbench, I set my
> path in the IDL Preferences, and make sure none
> of my projects "update" the path. If I'm not using
> a workbench, I set my IDL path in my startup file,
> using EXPAND_PATH to find sub-directories, as at the
> end of this article.
>
> http://www.dfanning.com/misc_tips/idlsetup.html
>
> Cheers,
>
> David
> --
> David Fanning, Ph.D.
> Fanning Software Consulting, Inc.
> Coyote's Guide to IDL Programming:http://www.dfanning.com/
> Sepore ma de ni thui. ("Perhaps thou speakest truth.")
Incidentally, I can relate from experience that when you have a
gazillion variables you want to put in a save file, SAVE, /ALL is not
the way to go. Since it also saves !PATH... and if you then try to
restore that file on a different system where things are located in
different places, you can get yourself very very confused!
-Jeremy.
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
