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

[Lennart Borgman]

Romain Francoise wrote:
> "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.

Maybe look into the compiled file if the first-guess source file does 
not exist?