From: Mark Oteiza <mvoteiza@udel.edu>
To: 21422@debbugs.gnu.org
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 [thread overview]
Message-ID: <20160107190640.GA28029@holos> (raw)
In-Reply-To: <87y4gl5ung.fsf@udel.edu>
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?
next prev parent reply other threads:[~2016-01-07 19:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-05 4:58 bug#21422: 25.0.50; apropos-library on libraries using cl-def{generic,method} fails Mark Oteiza
2016-01-07 19:06 ` Mark Oteiza [this message]
2016-01-07 20:06 ` Eli Zaretskii
2016-01-07 23:35 ` Dmitry Gutov
2016-01-08 1:27 ` Glenn Morris
2016-01-08 12:14 ` Eli Zaretskii
2016-01-09 0:44 ` Glenn Morris
2016-01-08 1:27 ` Glenn Morris
2016-01-08 9:36 ` Eli Zaretskii
2016-01-09 0:44 ` Glenn Morris
2016-01-09 7:05 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160107190640.GA28029@holos \
--to=mvoteiza@udel.edu \
--cc=21422@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).