all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Stephen Leake <stephen_leake@stephe-leake.org>, emacs-devel@gnu.org
Subject: Re: xref-collect-references picks wrong search backend
Date: Fri, 11 Sep 2015 04:12:13 +0300	[thread overview]
Message-ID: <55F22A6D.10905@yandex.ru> (raw)
In-Reply-To: <86fv2m1dwa.fsf@stephe-leake.org>

On 09/10/2015 06:40 PM, Stephen Leake wrote:

> I have run Gnu Global on the Emacs root directory, mostly to find out if
> that's useful (so far not, because etags is better, but in other projects
> it could be useful).

Maybe you should run it in the src/ directory, not the top level one. 
This way, files outside of it won't try to use GNU Global.

> I'm actually using an experimental multi-language project setup that
> provides an xref-find-function that calls xref-collect-references
> directly for elisp searches, so I suggest the following solution:
>
> - Add an optional symref-tool arg to xref-collect-references; my
>    xref-find-function can set that to 'grep for elisp searches.

If you'll find that useful, sure.

But semantic-symref-find-references-by-name in the default 
implementation was just a way to get out something working quickly.

We might even have to bypass it altogether and always use Grep (in the 
default implementation), because any problems with semantic-symref (like 
GTAGS being out of date, or, like in this case, the tagging program 
skipping whole classes of files) are entirely opaque to the user.

 > elisp--xref-find-references could also set it to 'grep.

Since its definition is pretty much the same as the etags one, I was 
going to merge them and put in the new "default" backend.



  reply	other threads:[~2015-09-11  1:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-10 15:40 xref-collect-references picks wrong search backend Stephen Leake
2015-09-11  1:12 ` Dmitry Gutov [this message]
2015-09-11 15:57   ` Stephen Leake

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=55F22A6D.10905@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=stephen_leake@stephe-leake.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.