"Eric M. Ludlam" writes:
> I do not install my info files. I use C-u M-x info RET,
> typa-typa-typa-typa RET to view the CEDET info files.
But for the final user, I think it's important that such
details seem to be cleanly installed. "Emacs have a well known,
well defined documentation system, why my just installed new toy
doesn't deal properly with it? Where the world is the doc?"
> I don't know what the right thing to do for this is either. It makes
> sense to have the CEDET package build its own dir file for all
> internal tools. The info hook at the bottom also could go into the
> cedet-load script. I haven't used the info directory-list before.
There is a subtle issue with it. That's why we need the
'eval-after-load'. We can use 'Info-default-directory-list', but
if the former is already initilized, the value will be discarded
(never used, more exactly).
But if we use directly the former, before it's initialized, it
will never be properly initialized (because it have already one
item, so Emacs thinks it's already set up). So we'll never see
the "standard" Info files.
So the only reliable way I found to add directories to the Info
search path is to wait the load of the "info" package, then force
call to 'Info-initialize' (it does nothing if the path is set
up), and then add the directory to the path.
> I'd like to hear what others think about this install solution.
To explain the other parts... Using install-info on each
top-level Info file (those ending in ".info", w/o any trailing
number) adds a line for each in a file called "dir". When we use
'C-h i', Emacs search for such "dir" files in each directory in
'Info-directory-list', and merge all them, to make the Top Info
node we see when Info launches.
So when I 'C-h i', I can do 'g(emacs)', 'g(elisp)', 'g(eieio)',
'g(ede)', 'g(nxml)', etc., to directly go to these Info files.