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

Home » Public Forums » archive » IDL 7 on LINUX Question
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: IDL 7 on LINUX Question [message #57097 is a reply to message #57065] Mon, 03 December 2007 18:14 Go to previous message
Vince Hradil is currently offline  Vince Hradil
Messages: 574
Registered: December 1999
Senior Member
On Dec 3, 6:08 pm, JD Smith <jdsm...@as.arizona.edu> wrote:
> On Fri, 30 Nov 2007 14:09:00 -0800, Vince Hradil wrote:
>> 1- how does IDL-Wave for Emacs do this. Doesn't it build a "library" file
>> that keeps track of things like keywords and completions, etc. Then that
>> file can be quickly searched. Of course, if you change your library, you
>> have to re-scan the files, but I find this not too inconvenient.
>
> You pre-scan and it creates .idlwave_catalog files. You can rescan
> easily, but until you do, nothing changes. Any files loaded in a buffer,
> or routines compiled *do* update, so typically things stay in reasonable
> sync.
>
> JD

Thanks for the reply, JD. The more I play with the new IDE, the more
I think I'm going to stick with emacs. Of course, I've been using
emacs for about 15-20 years now, so that could have a lot to do with
my bias. I really think that the IDLDE could have used a "catalog"
approach, but maybe it is just the way things are normally done in
Eclipse - i.e. rescan the active path upon loading the ide. Any JAVA
(or other) developers out there that use Eclipse? Of course, JAVA and
IDL are completely different beasts when it come to deployment (or are
they really...?)
[Message index]
 
Read Message
Read Message
Previous Topic: Re: IDL 7 on LINUX Question
Next Topic: Poor ENVI performance on dual CPU - quad core

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

Current Time: Fri Oct 10 18:57:08 PDT 2025

Total time taken to generate the page: 0.96143 seconds