all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stephen Leake <stephen_leake@stephe-leake.org>
To: emacs-devel@gnu.org
Subject: Re: adding xref-find-definitions support for cl-defmethods
Date: Sun, 09 Aug 2015 08:18:14 -0500	[thread overview]
Message-ID: <86y4hkzjl5.fsf@stephe-leake.org> (raw)
In-Reply-To: <8637zs1u8s.fsf@stephe-leake.org> (Stephen Leake's message of "Sun, 09 Aug 2015 08:12:03 -0500")

Stephen Leake <stephen_leake@stephe-leake.org> writes:

> I'd like xref-find-definitions to show all loaded cl-defmethods, as
> describe-function does.
>
> So I'm adding a function cl-generic--xref-locs to return a list of xref
> locations, in cl-generic.el.
>
> That will be called from elisp--xref-identifier-location for a new
> 'defgeneric type.
>
> Can elisp-mode.el have (require 'cl-generic')? I remember some
> discussion about limits on what elisp-mode.el can require, related to
> preloading things. But there's nothing in the header comments about that.
>
> If not, should I put cl-generic--xref-locs in elisp-mode (or xref?)
>
> On the other hand, there may be other types that could be added to
> xref-find-definitions, possibly by ELPA packges. So perhaps an alist of
> (type . loc-function), processed in elisp--xref-find-definitions, would
> be appropriate.
>
> Actually, there's no need for the type symbol; it's only used by
> elisp--xref-find-definitions and elisp--xref-identifier-location. So
> that could be eliminated, and the current code restructured around a
> list of loc-functions, as describe-function is with the hook
> help-fns-describe-function-functions.

On further thought, it's pretty clear that anything describe-function
can handle, xref-find-definition should handle. So both should have
similar lists.

-- 
-- Stephe



  reply	other threads:[~2015-08-09 13:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-09 13:12 adding xref-find-definitions support for cl-defmethods Stephen Leake
2015-08-09 13:18 ` Stephen Leake [this message]
2015-08-09 16:36   ` Stephen Leake
2015-08-09 16:24 ` Stefan Monnier

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86y4hkzjl5.fsf@stephe-leake.org \
    --to=stephen_leake@stephe-leake.org \
    --cc=emacs-devel@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.