Re: find-library-name fails if file (with no extension) exists.

[Romain Francoise]

"Juanma Barranquero" <address@hidden> writes:

> The current behavior, then, has the problem that compiling files with
> no extension, or non-default ones:

>  mylib => mylib.elc
>  mylib.dat => mylib.dat.elc

> but help from describe-function and friends points to nonexistent
> "mylib.el" and "mylib.dat.el".

Yes, because of `describe-simplify-lib-file-name'...

The reliable approach would be to look into the compiled file, it
contains the source file's name.  But it would be overkill.

-- 
Romain Francoise <address@hidden> | The sea! the sea! the open
it's a miracle -- http://orebokech.com/ | sea! The blue, the fresh, the
                                        | ever free! --Bryan W. Procter