Open duckworthd opened 11 years ago
Thanks for the bug report! I have some questions:
:UpdateTags
or do you pass it one or more arguments?vim-easytags
plug-in to use a global tags file?easytags_autorecurse
option enabled? You can check by executing the command :let g:easytags_autorecurse
(it will print a 0 or 1).--recurse=yes
and --file-scope=no
optionsg:easytags_cmd
, g:easytags_file
, and have disabled g:easytags_on_cursorhold
g:easytags_autorecurse
is not definedI just tried running :UpdateTags
without any options and setting g:easytags_autorecurse = 1
and absolute paths did appear in my tag file (yay!). Problem solved! Could you describe how this behavior manifested for my benefit?
The vim-easytags
plug-in executes Exuberant Ctags in one of two modes:
The two modes are not handled in exactly the same way so it could be that one of the two modes normalizes pathnames while the other does not. I'll see if I can find out and fix it (vim-easytags
should work regardless of how you execute Exuberant Ctags).
Action: Running
:UpdateTags
with a directory containing python filesSymptom: all file names referenced in my tag file have paths relative to the location where I executed
:UpdateTags
, e.g.Observed Output Vim interprets the file's location as relative to the tag file,
Expected Output Jumping to the relevant file