|Re: xref rocks!
|Tue, 26 Apr 2016 23:35:33 -0400
On 04/26/2016 08:12 PM, Robert Weiner wrote:
One thing that would help would be better
separation between finding xrefs (which should just return lists of
them) and displaying xrefs. For example, I went looking for a generic
xref equivalent to find-tag-noselect and the only thing I found was
something specific to elisp tags.
Are you looking for
(xref-backend-definitions (xref-find-backend) "car")
Also, there seem to be many functions that just call a single other
functions, creating a deeply nested tree of calls. Is there a way to
Could you give an example?
I also see that about a year ago there was a call for documenting
xref.el. Has any progress been made on that? Even though things will
change, writing the documentation will give you a base that you can
adapt as the library evolves and will help people to provide further
There is an introduction in Commentary at the top of xref.el. You can read it, among other ways, using `M-x describe-package RET xref RET'.
|[Prev in Thread]
|[Next in Thread]