Menu

#278 --tag-relative mangling file paths

open
nobody
None
5
2010-05-04
2010-05-04
Jon Tanner
No

Running Ubuntu 10.04. Installed ctags from repo.

Running this command (where ../../Source is the top directory in the code base):

ctags -R --fields=+i --tag-relative=yes -f tags ../../Source

produces listings that are mangled in such a way that the first named directory (in this case Source) has the last two letters in it replaced by the 7th & 8th letters in the next directory. For example:

../../Source/SomeFooDir/foo.c

becomes

../../SouroD/SomeFooDir/foo.c

Even better is if it's exactly 6 characters:

../../Source/FooDir/foobar.c

becomes

../../Sour/f/FooDir/foobar.c

I searched, and found no other entries for this problem. Is --tag-relative a deprecated option?

Discussion

  • Jon Tanner

    Jon Tanner - 2010-05-04

    I would also note that this did not occur under Ubuntu 9.04, which I just recently upgraded from.

     
  • James Newton

    James Newton - 2010-05-19

    I see the same type of behavior if I do:

    ctags-exuberant -R -e ./src

    with a relative path on the command line. It works correctly if its just 'src'. It also seems to work with './src' but without the -e flag.

     
  • Chad Austin

    Chad Austin - 2010-12-01

    I also see this problem on Ubuntu 10.04. Before, I'd been using Debian Sarge, Mac OS X, and Windows, and hadn't seen this bug.

     
  • Jon Buckingham

    Jon Buckingham - 2011-12-13

    I also see this problem when using etags with relative file names.
    e.g.
    etags ../../another/dir/file.c

    results in a TAGS file with garbled path name.
    I am using linux: opensuse 11.4 64bit.
    ctags rpm: ctags-2009.12.21-6.4.x86_64

     

Log in to post a comment.