Re: idltags? [message #31689] |
Mon, 05 August 2002 12:58  |
JD Smith
Messages: 850 Registered: December 1999
|
Senior Member |
|
|
On Mon, 05 Aug 2002 12:17:42 -0700, William Daffer wrote:
> shawn@young.net (Shawn) writes:
>
>> Hello,
>> I am interested in getting something that makes a "tags" file for
>> idl, the kind ctags makes. I have found references to idltags in the
>> archives of this group, but am not sure that it is what I am looking
>> for. I have tried to download it from the anonymous ftp site by
>> following a link posted on the website,
>> http://www.gsf.de/ILIAD/software/IDL/idl_www_sites.html. But the link
>> is dead. So, does anyone know if this software is still available, and
>> does it make a ctags type file that I can use with "Vim" (Vi Improved)?
>> Thanks,
>> Shawn
>
> If you're an emacs user, look up idlwave-mode at http://idlwave.org/
> It uses etags to generate a tags table. If not, but you're still a
> unix user you might grab etags. The command that's called by
> idlwave-shell to generate the tags file is:
>
>
> etags --output=IDLTAGS --language=none \
> --regex='/[\\t]*[pP][Rr][Oo][ \\t]+\\([^ \\t,]+\\)/' \
> --regex='/[\\t]*[Ff][Uu][Nn][Cc][Tt][Ii][Oo][Nn][ \\t]+\\([^
> \\t,]+\\)/' \
> foo.pro [... bar.pro ... etc.]
>
> where the newlines have been escaped for readibility.
>
>
> or
>
> etags --out...blah blah blah... ./dir1/*.pro [ ... ./dir2/*.pro ...
> etc.]
For vi, he'll want the ctags version of this call, which is the default
within the perl script "idltags". Is anyone actually using the IDLTAGS
mechanism within Emacs and IDLWAVE? They seem to have been superseded in
all ways by the user catalog.
I'd also like to gauge interest in the possibility of having multiple user
catalogs and system catalogs, which can be built automatically (e.g. in a
cron job). For instance, all system libraries (like NasaLib, etc.) could
have a relatively static, site-wide catalog available to everyone on the
system, and one or more transient personal libraries could be stored in the same
way a user catalog is now. Eventually, I'd like to convince the large
package maintainers to build and bundle such an IDLWAVE catalog with their
packages, which would be found automatically, relieving the user the need to
build them, and providing a much larger collection of routines IDLWAVE
knows about without being told to look.
JD
|
|
|