| Preferences gone mad [message #73580] |
Thu, 18 November 2010 11:07 |
penteado
Messages: 866
Registered: February 2018
|
Senior Member
Administrator |
|
|
It appears that a previously well behaved IDL installation has gone
crazy with preference setting for one user. For other users on the
same computer, things look normal. And the same seems to occur from
the Workbench or the command line:
IDL> p=pref_get('IDL_PATH')
IDL> print,p
+/usr/local/gpulib:<IDL_DEFAULT>
IDL> p+=':+/some_directory/'
IDL> print,p
+/usr/local/gpulib:<IDL_DEFAULT>:+/some_directory/
IDL> pref_set,'IDL_PATH',p,/commit
IDL> print,pref_get('IDL_PATH')
+/usr/local/gpulib:<IDL_DEFAULT>:+/some_directory/
IDL> exit
Then, from a new session:
IDL> print,pref_get('IDL_PATH')
+/usr/local/gpulib:<IDL_DEFAULT>
Where did the new preference go?
The preferences file was updated; it contains:
IDL_PATH : +/usr/local/gpulib:<IDL_DEFAULT>:+/some_directory/
The same happens if I change the path from the Workbench. It seems
that IDL is ignoring the preferences file. I already removed the
entire .idl directory, to let it be recreated, and it made no
difference. The gpulib directory shows up because there is an IDL_PATH
environment variable.
Am I going mad? Am I missing something?
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
