You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Despite there being a fairly recent commit (0d4ae14) intended to fix this problem, it looks like I'm still running into the problem. It appears that my tags setting in my .vimrc is being clobbered by vim-ruby. I have :set tags+=./tags; in my .vimrc but when I open VIM on a file and type :set tags to see what it thinks the currently set value is, I get only the Ruby paths (which appear to be set from line 98 of the above linked to commit). This results in VIM not being able to see my tags file for my codebase. If I source my .vimrc afterward, then the tags setting has my path plus the Ruby paths. I do not run into this problem when I remove vim-ruby altogether.
I am running pathogen to manage VIM bundles and bring in vim-ruby. I'm also using Exuberant Tags and VIM 7.3.
The text was updated successfully, but these errors were encountered:
Looks like when I fixed it to preserve the local 'tags', I stopped preserving the global one. Fix is obvious, though I leave it to you to check that it works. Thanks.
Despite there being a fairly recent commit (0d4ae14) intended to fix this problem, it looks like I'm still running into the problem. It appears that my
tags
setting in my.vimrc
is being clobbered by vim-ruby. I have:set tags+=./tags;
in my.vimrc
but when I open VIM on a file and type:set tags
to see what it thinks the currently set value is, I get only the Ruby paths (which appear to be set from line 98 of the above linked to commit). This results in VIM not being able to see mytags
file for my codebase. If I source my.vimrc
afterward, then thetags
setting has my path plus the Ruby paths. I do not run into this problem when I remove vim-ruby altogether.I am running pathogen to manage VIM bundles and bring in vim-ruby. I'm also using Exuberant Tags and VIM 7.3.
The text was updated successfully, but these errors were encountered: