GNU bug report logs - #28403
25.2; find-tag works, but xref-find-definitions doesn't; bug?

Previous Next

Package: emacs;

Reported by: Winston <wbe <at> psr.com>

Date: Sat, 9 Sep 2017 22:41:02 UTC

Severity: normal

Found in version 25.2

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Winston <wbe <at> psr.com>
Cc: 28403 <at> debbugs.gnu.org, dgutov <at> yandex.ru
Subject: bug#28403: 25.2; find-tag works, but xref-find-definitions
Date: Mon, 11 Sep 2017 05:31:20 +0300
> Date: Sun, 10 Sep 2017 16:12 EDT
> From: Winston <wbe <at> psr.com>
> Cc: dgutov <at> yandex.ru, 28403 <at> debbugs.gnu.org
> 
> Eli suggested:
> > ... here's how I suggest you invoke etags to solve the
> > problems with the _ARGS# macros:
> > 
> >   etags --regex="/[ \t]*\([^ \t]+\)[ \t]+_ARGS/\1/" ...
> 
>    I don't think that quite works

It worked with your example.

>    etags --regex="/\([^ ]+\) +_ARGS[0-9]+/\1/" ...
> 
> would work as well?

As long as you understand the principles, it's in your hands.

> Does regex have an implicit '^'?

Yes (as explained in the manual).

>    [Too bad etags doesn't have a way of doing "s/[ \t]+_ARGS[0-9]*//" on
> the lines it normally finds...]

Why do you need that?

>    OK.  I like that approach better than having to do the setq,
> especially since putting a suitable etags command in a makefile is easy.
> That also has the benefit of tying the fix to the code written in that
> style, rather than making a global change that would affect other code I
> work on.

Right.

I guess we can now close the bug report?




This bug report was last modified 7 years and 253 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.