unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Bob Rogers <rogers@modulargenetics.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 22947@debbugs.gnu.org
Subject: bug#22947: 25.0.92; xref-find-definitions fails for Perl & etags
Date: Tue, 8 Mar 2016 21:43:48 -0500	[thread overview]
Message-ID: <22239.36324.478948.721025@gargle.gargle.HOWL> (raw)
In-Reply-To: <88256367-3f1d-6dda-a509-d89e3c8e6c28@yandex.ru>

   From: Dmitry Gutov <dgutov@yandex.ru>
   Date: Wed, 9 Mar 2016 03:52:43 +0200

   Hi Bob,

   On 03/08/2016 08:27 PM, Bob Rogers wrote:

   > The bug is that, no matter how many perl_method_name definitions exist
   > in the TAGS file, xref-find-definitions won't find any of them, because
   > it's only looking for an exact match to what Perl considers the
   > package-qualified name, namely the "Perl::Package::perl_method_name" as
   > it appears in this TAGS line:
   >
   > 	sub perl_method_name ^?Perl::Package::perl_method_name^A23,321

   This seems to indicate a problem in etags. Were you using the "real" 
   etags, one that's developed and distributed together with Emacs? Did it 
   come with the development snapshot your bug report was sent from?

Yes, and yes.

   If so, please send a small sample of Perl code we can reproduce the 
   problem in.

Try this:

   1.  git clone git@github.com:rgrjr/meals.git

   2.  cd meals

   3.  etags *.pl

and then continue with step two in the original recipe.  (This is a
small hack; the clone should only be half a megabyte.)  You can try
M-. on parse_recipes (one definition) or add_ingredient (two
definitions).

					-- Bob





  reply	other threads:[~2016-03-09  2:43 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 [this message]
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

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=22239.36324.478948.721025@gargle.gargle.HOWL \
    --to=rogers@modulargenetics.com \
    --cc=22947@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    /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).