[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#21422: 25.0.50; apropos-library on libraries using cl-def{generic,me
From: |
Mark Oteiza |
Subject: |
bug#21422: 25.0.50; apropos-library on libraries using cl-def{generic,method} fails |
Date: |
Thu, 7 Jan 2016 14:06:40 -0500 |
User-agent: |
Mutt/1.5.24+44 (9480a363a68a) (2015-08-30) |
On 05/09/15 at 12:58am, Mark Oteiza wrote:
>
> From emacs -Q:
>
> M-x apropos-library RET cl-generic RET
>
> Debugger entered--Lisp error: (wrong-type-argument symbolp
> (cl-generic-generalizers (head eql)))
> apropos-symbols-internal((cl--generic-typeof-generalizer
> cl--generic-typeof-types cl--generic-struct-generalizer
> cl--generic-struct-specializers cl--generic$
> apropos-library("cl-generic")
> funcall-interactively(apropos-library "cl-generic")
> call-interactively(apropos-library record nil)
> command-execute(apropos-library record)
> execute-extended-command(nil "apropos-library" nil)
> funcall-interactively(execute-extended-command nil "apropos-library" nil)
> call-interactively(execute-extended-command nil nil)
> command-execute(execute-extended-command)
>
> I came across this because doing M-. on a function defined with
> cl-defgeneric and cl-defmethod doesn't go to the definition, just the
> top of the library, so apropos-library was my backup. I don't know if
> the xref behavior should be a separate report.
cl-generic is used pretty widely, and apropos-library fails on libraries
using it. Could this be marked to be fixed before release?