| Re: idlwave library catalog for local directory? [message #54797] |
Fri, 13 July 2007 10:35 |
JD Smith
Messages: 850
Registered: December 1999
|
Senior Member |
|
|
On Thu, 05 Jul 2007 07:44:44 -0700, Mike wrote:
> I'm finally trying to switch my habits from using tags files to
> idlwave library catalogs, but I'm having trouble trying to figure out
> how to use it. Suppose I have a directory with a number of .pro files
> in it, and I'm actively developing them. With etags, I'd generate a
> tags file with idltags and just use it as any other tags file. With
> idlwave's library catalogs, the instructions say to make a catalog
> with idlwave_catalog and to load it by starting an idl shell and
> running idlwave-create-user-catalog-file.
There are two flavors of catalogs in IDLWAVE: the old outdated
user-catalog (everything gets piled into one file in ~/.idlwave) and
the new spiffy library catalog (little .idlwave_catalog files
sprinkled like cereal sugar nuggets throughout your directories).
The latter is much easier to deal with, but does require perl, and
runs outside of Emacs using the perl script idlwave_catalog you
received with your IDLWAVE install.
I simply run it like this:
% cd /path/to/my/library
% /path/to/idlwave_catalog MYLIB
where MYLIB is some unique name for your library. You can have any
number of nested sub-directories there. I even have a cron job which
does this for me nightly, to keep up to date. If /path/to/my/library
is on your IDL_PATH, idlwave will find your catalog files and load
them automagically. You'll also see the catalog name under Sources
when you inquire routine info, e.g.:
Usage: Result = READFITS(filename, header, heap)
Keywords: CHECKSUM COMPRESS EXTEN_NO HBUFFER NANVALUE NO_UNSIGNED NOSCALE
NSLICE NUMROW POINTLUN SILENT STARTROW
Sources: - AstroLib [L---] /idl_library/nasa/pro/fits/readfits.pro
Those of you who use David's Coyote library, AstroLib, etc., will see
a brief flash of the name by when you first load IDLWAVE, as these
catalogs get loaded. If you too distribute a library, consider
running idlwave_catalog on it before packaging it up, for the
convenience of your users (the .idlwave_catalog files are tiny).
JD
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
