From: Dmitry Gutov <dgutov@yandex.ru>
To: Bob Rogers <rogers@modulargenetics.com>, Eli Zaretskii <eliz@gnu.org>
Cc: 22947@debbugs.gnu.org
Subject: bug#22947: 25.0.92; xref-find-definitions fails for Perl & etags
Date: Fri, 11 Mar 2016 03:28:29 +0200 [thread overview]
Message-ID: <be320f44-36b0-0c3b-50dc-6c9b0bd37cca@yandex.ru> (raw)
In-Reply-To: <22241.50645.374350.820199@gargle.gargle.HOWL>
On 03/10/2016 09:07 PM, Bob Rogers wrote:
> Also, FWIW, I thought I should mention that M-x find-tag works
> correctly with the existing etags output . . .
By default, find-tag-tag-order is set to a very lax list (in
etags-recognize-tags-table). In comparison,
etags-xref-find-definitions-tag-order is relatively strict.
We've decided to prefer the latter approach, because with lax matching
come more false positives. But users can modify the latter variable to
their liking as well.
prev parent reply other threads:[~2016-03-11 1:28 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 18:27 bug#22947: 25.0.92; xref-find-definitions fails for Perl & etags Bob Rogers
2016-03-09 1:52 ` Dmitry Gutov
2016-03-09 2:43 ` Bob Rogers
2016-03-10 13:20 ` Eli Zaretskii
2016-03-10 13:36 ` Dmitry Gutov
2016-03-10 14:16 ` Eli Zaretskii
2016-03-10 14:34 ` Dmitry Gutov
2016-03-10 15:31 ` Eli Zaretskii
2016-03-10 15:50 ` Dmitry Gutov
2016-03-10 16:22 ` Eli Zaretskii
2016-03-11 1:45 ` Dmitry Gutov
2016-03-11 8:04 ` Eli Zaretskii
2016-03-11 12:46 ` Dmitry Gutov
2016-03-11 14:59 ` Eli Zaretskii
2016-03-12 1:08 ` Dmitry Gutov
2016-03-12 7:41 ` Eli Zaretskii
2016-03-12 12:10 ` Dmitry Gutov
2016-03-12 12:33 ` Eli Zaretskii
2016-03-12 12:46 ` Dmitry Gutov
2016-03-12 16:09 ` Eli Zaretskii
2016-03-10 19:07 ` Bob Rogers
2016-03-10 20:32 ` Eli Zaretskii
2016-03-11 18:08 ` Bob Rogers
2016-03-11 18:34 ` Eli Zaretskii
2016-03-11 19:05 ` Bob Rogers
2016-03-12 0:50 ` Dmitry Gutov
2022-04-26 12:40 ` Lars Ingebrigtsen
2022-04-26 17:00 ` Bob Rogers
2022-04-27 12:14 ` Lars Ingebrigtsen
2016-03-11 1:28 ` Dmitry Gutov [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=be320f44-36b0-0c3b-50dc-6c9b0bd37cca@yandex.ru \
--to=dgutov@yandex.ru \
--cc=22947@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rogers@modulargenetics.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 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.