bug#5661: 23.1.92; `find-library-name' should find a loaded library

bug#5661: 23.1.92; `find-library-name' should find a loaded library

[Drew Adams]

emacs -Q

Put this code in a new file throw-a.el in a directory that is not in your
`load-path':

(defun foo () (message "foo"))
(provide 'throw-a)

In that same directory, do this:

M-x load-file RET throw-a.el RET
M-x load-library RET find-func RET
M-: (find-library-name "throw-a") RET

It should find the library (since it was loaded and thus provided), but instead
it raises an error:

Debugger entered--Lisp error: (error "Can't find library throw-a")
  signal(error ("Can't find library throw-a"))
  error("Can't find library %s" "throw-a")
  find-library-name("throw-a")
  eval((find-library-name "throw-a"))
  eval-expression((find-library-name "throw-a") nil)
  call-interactively(eval-expression nil nil)

The doc string says nothing about searching only the `load-path'. It's
reasonable to think that this should be able to find the library either by
checking loaded libraries or by searching the `load-path'.

Consider, for example, using `finder-commentary' after having loaded the library
using `load-file' but not having the library in the `load-path'. The library is
known to the current session, but Emacs isn't smart enough to find it.

bug#5661: 23.1.92; `find-library-name' should find a loaded library

[Lars Ingebrigtsen]

"Drew Adams" <drew.adams@oracle.com> writes:

> Put this code in a new file throw-a.el in a directory that is not in your
> `load-path':
>
> (defun foo () (message "foo"))
> (provide 'throw-a)
>
> In that same directory, do this:
>
> M-x load-file RET throw-a.el RET
> M-x load-library RET find-func RET
> M-: (find-library-name "throw-a") RET
>
> It should find the library (since it was loaded and thus provided), but instead
> it raises an error:
>
> Debugger entered--Lisp error: (error "Can't find library throw-a")
>   signal(error ("Can't find library throw-a"))
>   error("Can't find library %s" "throw-a")
>   find-library-name("throw-a")
>   eval((find-library-name "throw-a"))
>   eval-expression((find-library-name "throw-a") nil)
>   call-interactively(eval-expression nil nil)
>
> The doc string says nothing about searching only the `load-path'. It's
> reasonable to think that this should be able to find the library either by
> checking loaded libraries or by searching the `load-path'.

That would be nice.  But does Emacs have a record of all files it has
done `load-file' on somewhere?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#5661: 23.1.92; `find-library-name' should find a loaded library

[Drew Adams]

> > The doc string says nothing about searching only the `load-path'. It's
> > reasonable to think that this should be able to find the library either
> by
> > checking loaded libraries or by searching the `load-path'.
> 
> That would be nice.  But does Emacs have a record of all files it has
> done `load-file' on somewhere?

Sorry, I'm reading these really quickly.  But does `load-history'
apply here?

bug#5661: 23.1.92; `find-library-name' should find a loaded library

[Lars Ingebrigtsen]

Drew Adams <drew.adams@oracle.com> writes:

>> > The doc string says nothing about searching only the `load-path'. It's
>> > reasonable to think that this should be able to find the library either
>> by
>> > checking loaded libraries or by searching the `load-path'.
>> 
>> That would be nice.  But does Emacs have a record of all files it has
>> done `load-file' on somewhere?
>
> Sorry, I'm reading these really quickly.  But does `load-history'
> apply here?

Indeed it seems like that should do the trick.  Does anybody object to
me extending `find-library-name' to check with `load-history' after it's
gone through the paths it's currently searching?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#5661: 23.1.92; `find-library-name' should find a loaded library

[Lars Ingebrigtsen]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Drew Adams <drew.adams@oracle.com> writes:
>
>>> > The doc string says nothing about searching only the `load-path'. It's
>>> > reasonable to think that this should be able to find the library either
>>> by
>>> > checking loaded libraries or by searching the `load-path'.
>>> 
>>> That would be nice.  But does Emacs have a record of all files it has
>>> done `load-file' on somewhere?
>>
>> Sorry, I'm reading these really quickly.  But does `load-history'
>> apply here?
>
> Indeed it seems like that should do the trick.  Does anybody object to
> me extending `find-library-name' to check with `load-history' after it's
> gone through the paths it's currently searching?

Nobody seemed to object, so I've now implemented it.  It was more
twiddly than I assumed.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no