comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » File_Which What!?
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: File_Which What!? [message #33010 is a reply to message #32920] Thu, 21 November 2002 09:39 Go to previous messageGo to previous message
R.G. Stockwell is currently offline  R.G. Stockwell
Messages: 363
Registered: July 1999
Senior Member
David Fanning wrote:


> Humm, well, further tests this morning show that the file
> can be found if the directory containing it
> is *explicitly* on the path. That is, the directory
> is named specifically in File->Preferences->Path.
> If the directory containing the file is implicitly
> on the path (I.e., I have selected a check box for
> the parent directory in File->Preferences->Path)
> then the file can't be found.
>
> Bummer. :-(
>
> Cheers,
>
> David


works ok here (idl 5.5a, redhat linux), and I do not have the path set explicitly.



IDL> print,file_which('file.clt')
/home/stockwel/idllib/boblib/cora/qscat/interpolation/3d/dev el/file.clt

I do notice though that is only finds one instance of the file, apparently the
first one it finds in the path.

Are you in idl 5.6? (ms-win?)

Cheers,
bob stockwell

PS I "agree" with the first position optional argument for this function.
It is natural to use this order (path,file) when calling it, and
path is indeed optional, in that I'd almost always use it without setting path.
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Re: Structure Pass By Reference?
Next Topic: Re: sec : U Re: De-sensitizing individual list elements

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Fri Oct 10 03:05:10 PDT 2025

Total time taken to generate the page: 0.23907 seconds