From: Kaushal Modi <kaushal.modi@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>, Eli Zaretskii <eliz@gnu.org>
Cc: Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: Re: xref-find-references in elisp (Was: Re: grep-at-point)
Date: Wed, 11 Jan 2017 23:24:37 +0000 [thread overview]
Message-ID: <CAFyQvY0hrA55DRCCqYOeeHO1D3e3f7DgAb-0aAEhTt=_km-5cQ@mail.gmail.com> (raw)
In-Reply-To: <fb5e3915-0e5c-059e-5f73-126819eb9dc7@yandex.ru>
On Wed, Jan 11, 2017 at 6:14 PM Dmitry Gutov <dgutov@yandex.ru> wrote:
> On 12.01.2017 01:15, Kaushal Modi wrote:
>
> > Correct me if I am wrong, but it looks like semantic/symref is not used
> at
> > all by xref-find-references (probably in emacs-lisp-mode only?)
>
> The package is used. Semantic's parsers are not used, though.
>
Correct. I was doing (featurep 'symref) by mistake instead of (featurep
'semantic/symref).
>
> > So regardless of availability of idutils or global, it just
> > uses elisp--xref-find-definitions.
>
> Not true. That function is for definitions.
>
Yes, I am only talking about the case when xref-find-references is used. It
doesn't use global or idutils for that. After calls to
xref-find-references, the value of semantic-symref-tool stays at 'detect.
Only after I do M-: semantic-symref-detect-symref-tool, the value of
semantic-symref-tool changes to 'global (because I have GPATH file
generated in rootdir).
So global is not used at all by xref-find-references.
> > So if I call xref-find-references in an emacs-lisp-mode buffer,
> > semantic/symref is never required and
> `semantic-symref-detect-symref-tool'
> > is never called.
>
> Both things happen over here.
>
It was my mistake earlier; semantic/symref IS required. But
semantic-symref-detect-symref-tool doesn't seem be called at all because
the semantic-symref-tool value stays at 'detect unless I call
semantic-symref-detect-symref-tool manually.
Can you confirm the above?
--
Kaushal Modi
next prev parent reply other threads:[~2017-01-11 23:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 17:48 grep-at-point Joe Riel
2017-01-11 19:21 ` grep-at-point Aleksandar Simic
2017-01-11 19:55 ` grep-at-point Kaushal Modi
2017-01-11 19:42 ` grep-at-point Eli Zaretskii
2017-01-11 20:20 ` grep-at-point Kaushal Modi
2017-01-11 20:23 ` grep-at-point Eli Zaretskii
2017-01-11 21:09 ` grep-at-point Kaushal Modi
2017-01-11 21:32 ` grep-at-point Kaushal Modi
2017-01-11 21:45 ` grep-at-point Marcin Borkowski
2017-01-11 19:56 ` grep-at-point Eric Abrahamsen
2017-01-11 20:15 ` grep-at-point John Mastro
2017-01-11 20:46 ` grep-at-point Thien-Thi Nguyen
2017-01-11 21:01 ` grep-at-point Drew Adams
2017-01-11 21:29 ` grep-at-point Joe Riel
2017-01-11 22:15 ` xref-find-references in elisp (Was: Re: grep-at-point) Kaushal Modi
2017-01-11 23:14 ` Dmitry Gutov
2017-01-11 23:24 ` Kaushal Modi [this message]
2017-01-11 23:37 ` Dmitry Gutov
2017-01-11 23:42 ` Kaushal Modi
2017-01-11 23:42 ` grep-at-point Drew Adams
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='CAFyQvY0hrA55DRCCqYOeeHO1D3e3f7DgAb-0aAEhTt=_km-5cQ@mail.gmail.com' \
--to=kaushal.modi@gmail.com \
--cc=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--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.
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).