Re: New Release of XEmacs-Packages

Raymond> The package was found in ~/.xemacs automagically. Yes, that was clear from your earlier message. Raymond> The problem was that ilisp wanted to find out where it Raymond> was loaded from, so it grovels over load-path to find Raymond> some ilisp file. There ought to be an API for this. Ask Michael Sperber.... Raymond> Unfortunately, my load-path didn't include anything from Raymond> my ~/.xemacs packages, so ilisp couldn't really find out Raymond> where it was loaded from. This is what surprised me. AFAIK the library loading code does _not_ normally look at the package path variables; these are used to determine what goes into the load path. The load path is determined by taking certain defaults from paths.h (normally empty), EMACSLOADPATH, certain places relative to the XEmacs binary file, and then groveling over the various package paths. The latter operation is quite expensive (large numbers of stat calls), so the result is then cached in `load-path'. But it was my understanding that they would only be entered in `load-path' if Lisp libraries were found there. Raymond> Instead, it got it from my load-path which pointed to the Raymond> "global" xemacs packages directory. (Hmm, why does my Raymond> load-path have that?) -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."