esheldon / sdssidl

Automatically exported from code.google.com/p/sdssidl
1 stars 0 forks source link

which.pro does not search current working directory first for programs #3

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Make a new directory and copy a program in your IDL path to the new 
directory.  
2. Change to the new directory and start IDL.
3. Call which.pro to find out which version of the program you are using.  If 
you put a print statement in the copy in your working directory, you will see 
that IDL calls the copy in your working directory.  However, which.pro only 
finds the copy in your IDL path. 

What is the expected output? What do you see instead?
I would expect that which.pro would search the current working directory first 
since IDL uses programs in the current working directory before it looks in the 
IDL path.  If the two programs have a name collision, which.pro returns the 
location of the program in the IDL path.

What version of the product are you using? On what operating system?
I am using IDL 8.0 w/ sdssidl v1.7.0 w/ Linux

Original issue reported on code.google.com by becker.mr@gmail.com on 17 Feb 2012 at 1:29

GoogleCodeExporter commented 9 years ago
This has been fixed.

Original comment by becker.mr@gmail.com on 1 Apr 2012 at 6:47

GoogleCodeExporter commented 9 years ago

Original comment by becker.mr@gmail.com on 1 Apr 2012 at 6:47