From: Dmitry Gutov <dgutov@yandex.ru>
To: Winston <wbe@psr.com>, Eli Zaretskii <eliz@gnu.org>
Cc: 28403@debbugs.gnu.org
Subject: bug#28403: 25.2; find-tag works, but xref-find-definitions
Date: Mon, 11 Sep 2017 00:35:01 +0300 [thread overview]
Message-ID: <c20d356c-0969-143c-8ae9-ffd7b4f54094@yandex.ru> (raw)
In-Reply-To: <201709102119.v8ALJipg019297@psr.com>
On 9/11/17 12:18 AM, Winston wrote:
> * Find "foo" (partial name) didn't: rather than creating a window with
> the alternatives, it failed with "No definitions found for: foo".
That is because 'foo' is not defined in that file. And showing either of
the two lines as a match for it would be a false positive.
You should probably use project-find-regexp. Or use C-u M-x
xref-find-definitions with completion: you type 'foo', TAB, then see the
available tags that start with that string, pick one of them, and see
its definitions.
> find-tag given the same string "foo" went to the first one.
> xref-find-definitions with Dmitry's suggested change also worked
> (yesterday, without the special etags --regex TAGS, popping up a
> window with the alternatives).
>
> Any suggestions?
Just what I suggested before. But this problem is not related to your
use of macros anymore.
> -WBE
>
> P.S. Also, I'm finding it mildly annoying that xref-find-definitions,
> when next to just about any word, including text in comments, tries
> immediately to go to that word as a tag rather than prompting me
> for a name with the word as the default, as find-tag did. That
> means I'll have to remember to use my {arg} key fairly often to
> tell it "don't do that, prompt me." Is there an "always prompt"
> option, or do I need to write a trivial wrapper function?
You can customize xref-prompt-for-identifier to t.
next prev parent reply other threads:[~2017-09-10 21:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-09 22:40 bug#28403: 25.2; find-tag works, but xref-find-definitions doesn't; bug? Winston
2017-09-09 22:58 ` Drew Adams
2017-09-09 23:10 ` Dmitry Gutov
2017-09-10 2:50 ` bug#28403: 25.2; find-tag works, but xref-find-definitions Winston
2017-09-10 9:01 ` Dmitry Gutov
2017-09-10 14:29 ` Eli Zaretskii
2017-09-10 21:43 ` Dmitry Gutov
2017-09-11 2:38 ` Eli Zaretskii
2017-09-11 8:58 ` Dmitry Gutov
2017-09-11 14:43 ` Eli Zaretskii
2017-09-12 23:40 ` Dmitry Gutov
2017-09-13 15:32 ` Eli Zaretskii
2017-09-14 12:13 ` Dmitry Gutov
2017-09-14 17:13 ` Eli Zaretskii
2017-09-19 0:44 ` Dmitry Gutov
2017-09-19 3:58 ` Eli Zaretskii
2017-09-10 14:52 ` Winston
2017-09-10 18:27 ` Winston
2017-09-10 19:09 ` Eli Zaretskii
2017-09-10 19:06 ` Winston
2017-09-10 19:10 ` Winston
2017-09-10 20:12 ` Winston
2017-09-11 2:31 ` Eli Zaretskii
2017-09-10 21:19 ` Winston
2017-09-10 21:35 ` Dmitry Gutov [this message]
2017-09-11 2:34 ` Eli Zaretskii
2017-09-11 3:19 ` Winston
2017-09-11 4:05 ` Winston
2017-09-11 16:23 ` Eli Zaretskii
2017-09-11 4:11 ` Winston
2017-09-11 5:02 ` Winston
2017-09-11 16:51 ` Eli Zaretskii
2017-09-14 17:37 ` Winston
2017-09-14 22:08 ` Dmitry Gutov
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=c20d356c-0969-143c-8ae9-ffd7b4f54094@yandex.ru \
--to=dgutov@yandex.ru \
--cc=28403@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=wbe@psr.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).