Menu

#36 windows relative paths messed up.

closed-fixed
None
5
2002-07-16
2002-06-13
Anonymous
No

output with --verbose
OPENING .\win95\win_func.cpp as C++ language file
OPENING .\win95\wpchunk.cpp as C++ language file

however, the tags file
H:\dcdev\MyAvP\.\AFONT.C,518
#define UseLocalAssert ^?UseLocalAssert^A10,132

which makes the TAGS file completely useless outside
the directory it was created in.

for example, if I cd down a couple of levels, then in vim,

se tags=../../TAGS

this results in paths of the sort:

..\..\H:\dcdev\MyAvP\.\AFONT.C,518

please fix.

and no, --tag-relative does not help.

Discussion

  • Darren Hiebert

    Darren Hiebert - 2002-06-14
    • assigned_to: nobody --> dhiebert
    • status: open --> pending
     
  • Darren Hiebert

    Darren Hiebert - 2002-06-14

    Logged In: YES
    user_id=38016

    I need more information to diagnose this problem. Are you
    saying that you TAGS file contains this line?
    H:\dcdev\MyAvP\.\AFONT.C,518
    If so, then the problem is not in the generation of the tag
    file, but in the use of it, implying the problem is with
    Vim, not ctags. Please describe the ctags command line used
    to generate the TAGS file you give an example of.

     
  • Nobody/Anonymous

    Logged In: NO

    sorry, here's the complete info:

    ctags -e --recurse=yes --verbose=yes --tag-relative=yes .
    This is the command line to generate the tags.

    the tags then contain the absolute path as I mentioned in the
    original bug.

    with version 3.2.2, the TAGS file contains relative paths
    (i.e, .\afont.c instead of h:\myavp\afont.c)

    it seems to me that they should generate the same paths ?

    I'm using vim 5.3 and vim6.0 actually seems to work with both
    TAGs files. However, my question then is why is -tag-relative
    generating absolute paths ?

    thanks !

     
  • Nobody/Anonymous

    Logged In: NO

    sorry, here's the complete info:

    ctags -e --recurse=yes --verbose=yes --tag-relative=yes .
    This is the command line to generate the tags.

    the tags then contain the absolute path as I mentioned in the
    original bug.

    with version 3.2.2, the TAGS file contains relative paths
    (i.e, .\afont.c instead of h:\myavp\afont.c)

    it seems to me that they should generate the same paths ?

    I'm using vim 5.3 and vim6.0 actually seems to work with both
    TAGs files. However, my question then is why is -tag-relative
    generating absolute paths ?

    thanks !

     
  • Darren Hiebert

    Darren Hiebert - 2002-06-20
    • status: pending --> open
     
  • Darren Hiebert

    Darren Hiebert - 2002-07-11

    Logged In: YES
    user_id=38016

    I believe that I have fixed the problem. Please apply the
    attached patch and confirm that it corrects the problem. Let
    me know as soon as possible, as I would like to put out a
    new release with this fix.

     
  • Darren Hiebert

    Darren Hiebert - 2002-07-11

    Patch to fix problem

     
  • Darren Hiebert

    Darren Hiebert - 2002-07-16
    • status: open --> closed-fixed
     
  • Darren Hiebert

    Darren Hiebert - 2002-07-16

    Logged In: YES
    user_id=38016

    I am closing this due to lack of response from anonymous
    submitter who cannot be reached.

     

Log in to post a comment.