From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Tell xref to find definitions in Emacs' source code?
Date: Tue, 14 Nov 2017 11:42:41 -0800 [thread overview]
Message-ID: <87375gtzny.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 877eusptq7.fsf@gmail.com
Narendra Joshi <narendraj9@gmail.com> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Dmitry Gutov <dgutov@yandex.ru> writes:
>>
>>> On 10/31/17 9:31 PM, Eric Abrahamsen wrote:
>>>
>>>> Has anyone convinced xref to look up elisp definitions in a local git
>>>> clone of the Emacs source code, instead of the installed files? I'm
>>>> looking at building a tags table in the source directory, and then
>>>> adding a function to `elisp-xref-find-def-functions' that would try to
>>>> use the tags table to find a symbol in my git clone.
>>>>
>>>> Does anyone have anything like this on hand?
>>>
>>> The easiest way to do that is to build that clone and run Emacs from it.
>>>
>>> Like ./src/emacs.
>>>
>>> The alternative is to add xref-etags-mode to emacs-lisp-mode, and M-x
>>> visit-tags-table. Then you'll just use etags.
>>>
>>> Not sure if elisp-xref-find-def-functions can provide a
>>> straightforward alternative.
>>
>> Okay, thanks for the tips. I'll probably just do it the easy way and run
>> Emacs from the source directory.
> Or you can create a symbolic link (say ~/.local/bin/emacs) that points
> to $EMACS_SOURCE_DIR/src/emacs. That's how I have been using it.
Okay, good suggestion!
prev parent reply other threads:[~2017-11-14 19:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 19:31 Tell xref to find definitions in Emacs' source code? Eric Abrahamsen
2017-10-31 20:58 ` Nick Dokos
2017-10-31 21:04 ` Nick Dokos
2017-10-31 23:22 ` Eric Abrahamsen
2017-10-31 23:45 ` Dmitry Gutov
2017-11-01 0:24 ` Eric Abrahamsen
2017-11-14 19:04 ` Narendra Joshi
2017-11-14 19:42 ` Eric Abrahamsen [this message]
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=87375gtzny.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=help-gnu-emacs@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.