Re: hyperspec.el is compiled but can't be found in the load-path
Matt Tucker <tuck(a)whistlingfish.net> writes:
| -- Hannu Koivisto <azure(a)iki.fi> spake thusly:
|
| > hyperspec RET results to "No library hyperspec in search path" even
| > it exists, compiled even, under the extra directory which again is
| > under the same ilisp directory ilisp.elc resides in.
|
| hyperspec is located in the subdirectory "extra" under ilisp.
Yes, just like I said above.
| (locate-library "extra/hyperspec") finds it. This is how ilisp loads
| that file as well.
Well, I'm not interested in how ILISP loads it. I'm actually not
even interested in loading it or ILISP because I do ILISP
development so I have my own copy of it that I use and modify, but
what I'm interested in is that if I pretend to be a novice user who
wants to use ILISP and/or hyperspec and someone tells me "oh, since
you have that fancy and novice-friendly XEmacs and you installed
the SUMO tarball, you'll have ILISP and thus also hyperspec, so
they should Just Work, just like cc-mode Just Works (i.e. you can
say M-x c++-mode RET without writing autoload for c++-mode function
yourself and/or adding cc-mode's package directory to the
load-path), and, btw, the command you can use to check out the
source code of hyperspec is find-library", I'll be in a trouble
because they don't work. There are no autoloads for ILISP and
neither for hyperspec and its source can't be found unless you know
that it resides in a relative extra directory. Oh wait, it can't
be found even then; M-x locate-library RET extra/hyperspec RET
works but M-x find-library RET extra/hyperspec RET doesn't.
[Please respect my wishes, indicated in headers, not to be mailed
copies of followups.]
--
Hannu