| Re: Path Problems Redux [message #59526] |
Tue, 01 April 2008 11:23  |
Michael Galloy
Messages: 1114
Registered: April 2006
|
Senior Member |
|
|
On Apr 1, 11:29 am, David Fanning <n...@dfanning.com> wrote:
> Paul van Delst writes:
>> p.s. Just so we're jake, I want to stress my smiley's above are not laughing *at* you;
>> we're laughing *with* you. Maniacally.
>
> Well, try this on for size. I've given up--forever--letting
> IDL manage my PATH for me. So, I've decided all the new
> projects I'm creating will have the Manage Paths button
> turned off, and I will manage them myself.
>
> So, I created an IDL startup file with this in it:
>
> !PATH = 'G:\IDL\Coyote;' + $
> 'G:\IDL\CoyotePlus;' + $
> 'G:\IDL\Utilities;' + $
> Expand_Path('+G:\IDL\JHUAPL') + Path_Sep(/SEARCH_PATH) + $
> Expand_Path('+G:\IDL\Astronomy') + Path_Sep(/SEARCH_PATH) + $
> !PATH
>
> IDL starts up, the file executes (I know because there is also
> a print statement in there), and all is well. Except that my
> !PATH doesn't have *ANY* of these directories on it. However,
> if I do this:
>
> IDL> @fsc_startup
>
> Then the file executes for the 2nd time, and my directories are now
> on my PATH.
>
> Seriously, if I had a gun, I would be thinking about using it.
>
> How the %&#*@ do I put these files on my friggin' path so when
> I start IDL up I can get some work done!?
>
> Cheers,
>
> David
>
> P.S. When I get to the bottom of this problem, it is going to
> result in one of the best articles I've *ever* written!
Since you have started down this path (no pun intended), check out my
solution:
http://michaelgalloy.com/2008/04/01/path-management.html
It's a bit involved to setup, but very easy to change once you have it
going.
Mike
--
www.michaelgalloy.com
Tech-X Corporation
Software Developer II
|
|
|
|
|
|
|
|
| Re: Path Problems Redux [message #59532 is a reply to message #59528] |
Tue, 01 April 2008 10:29  |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Paul van Delst writes:
> p.s. Just so we're jake, I want to stress my smiley's above are not laughing *at* you;
> we're laughing *with* you. Maniacally.
Well, try this on for size. I've given up--forever--letting
IDL manage my PATH for me. So, I've decided all the new
projects I'm creating will have the Manage Paths button
turned off, and I will manage them myself.
So, I created an IDL startup file with this in it:
!PATH = 'G:\IDL\Coyote;' + $
'G:\IDL\CoyotePlus;' + $
'G:\IDL\Utilities;' + $
Expand_Path('+G:\IDL\JHUAPL') + Path_Sep(/SEARCH_PATH) + $
Expand_Path('+G:\IDL\Astronomy') + Path_Sep(/SEARCH_PATH) + $
!PATH
IDL starts up, the file executes (I know because there is also
a print statement in there), and all is well. Except that my
!PATH doesn't have *ANY* of these directories on it. However,
if I do this:
IDL> @fsc_startup
Then the file executes for the 2nd time, and my directories are now
on my PATH.
Seriously, if I had a gun, I would be thinking about using it.
How the %&#*@ do I put these files on my friggin' path so when
I start IDL up I can get some work done!?
Cheers,
David
P.S. When I get to the bottom of this problem, it is going to
result in one of the best articles I've *ever* written!
--
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.")
|
|
|
|
| Re: Path Problems Redux [message #59533 is a reply to message #59532] |
Tue, 01 April 2008 10:13 |
Paul Van Delst[1]
Messages: 1157
Registered: April 2002
|
Senior Member |
|
|
David Fanning wrote:
> C.E. Ordonez writes:
>
>> It turns out that when I installed 7.0 over an existing 6.4, the
>> installation "remembered" the name of the old startup file via a system
>> variable (IDL_STARTUP) inside a file named
>>
>> C:\Users\Ordonez\.idl\itt\pref-10-idl_7_0-windows\idl.pref
>
> Oh, my Gosh, that's it! That's where it was! You don't know
> how many hours of therapy you saved me from.
In my experience, when things are as weird as you experienced, it's usually a setting in
some as-yet-unknown preference file. But, the location and name above is just waaaay too
arcane to be taken seriously.
So what it is in the *nix version? Maybe all hidden files?
~/.idl/.itt/.pref-10-idl_7_0/.idl.pref
?
(Is this the 10'th incarnation of the v7.0 preferences?)
I mean, why should windows users have all the maddening, tear-your-hair-out-by-the-roots
fun? :o)
BTW, aren't the Design folks in the Marketing dept supposed to make the 'orrible prototype
interfaces more user-friendly?
> Well, shoot, I just blew my old IDL workspace completely away.
> Back to square one, I guess. Always good to get another chance
> at doing it right. :-(
If by doing it right you mean not using the Workbench then, based on the last few months
of posts about it in this newsgroup, I think you might be correct. ;o)
FWIW, I've had IDL 7.0 installed for a month or more now and, sans Workbench, I'm still as
productive as I was using 6.4. :o)
cheers,
paulv
p.s. Just so we're jake, I want to stress my smiley's above are not laughing *at* you;
we're laughing *with* you. Maniacally.
|
|
|
|
|
|
| Re: Path Problems Redux [message #59535 is a reply to message #59534] |
Tue, 01 April 2008 09:27 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
C.E. Ordonez writes:
> It turns out that when I installed 7.0 over an existing 6.4, the
> installation "remembered" the name of the old startup file via a system
> variable (IDL_STARTUP) inside a file named
>
> C:\Users\Ordonez\.idl\itt\pref-10-idl_7_0-windows\idl.pref
Oh, my Gosh, that's it! That's where it was! You don't know
how many hours of therapy you saved me from.
Well, shoot, I just blew my old IDL workspace completely away.
Back to square one, I guess. Always good to get another chance
at doing it right. :-(
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.")
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Path Problems Redux [message #59588 is a reply to message #59532] |
Wed, 02 April 2008 10:12 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
David Fanning writes:
> So, I created an IDL startup file with this in it:
>
> !PATH = 'G:\IDL\Coyote;' + $
> 'G:\IDL\CoyotePlus;' + $
> 'G:\IDL\Utilities;' + $
> Expand_Path('+G:\IDL\JHUAPL') + Path_Sep(/SEARCH_PATH) + $
> Expand_Path('+G:\IDL\Astronomy') + Path_Sep(/SEARCH_PATH) + $
> !PATH
>
> IDL starts up, the file executes (I know because there is also
> a print statement in there), and all is well. Except that my
> !PATH doesn't have *ANY* of these directories on it.
I've discovered this morning, that this way of setting
the PATH *does* work on LINUX machines running the IDL
Workbench. So, to reiterate, it does NOT work on Windows
but it DOES work on LINUX.
Still, this method is old school. Better to do it the new
way with Pref_Set, or from within the IDL Workbench IDL->Paths
preferences. Otherwise you will end up, as I have, with the
same directories on your path multiple times.
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming (www.dfanning.com)
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
