> Jason Aeschilman wrote: > > [ about the same tag being found in two tags files ] > > > Bram Moolenaar wrote: > > > First of all, it's recommended to upgrade to Vim 6.4. It includes many > > > bugfixes. > > > > > > But that doesn't solve this specific problem. I'll look into it. > > > > Bram, did you have a chance to look at this yet? > > Yes. It's not easy to figure out the full name of the file, so that > duplicate matches can be removed. I don't plan to do this for Vim 7. > > > Does anyone else know if there is a setting to get the old behavior > > back? I simply want vim to look at only the local tags file and if a > > match is found to jump. If and only if there is no match in the local > > tags file, it will consult the parent tags file, according to the "set > > tags=tags;/" setting I have in my .vimrc. > > The "very old behavior" was in fact wrong in a few other ways, some tags > would not be found. Thus you can't get this back, you were depending on > a bug.
First of all, I appreciate the help from you and Brett Stahlman. Thanks for following up on this. I'm a little confused though because in the help it says this under *tags-option*: The next file in the list is not used when: - A matching static tag for the current buffer has been found. - A matching global tag has been found. So if my tag is indeed in the current tags file, why would it even search the parent tags file? Again, my tags setting is "ctags=tags;/" as suggested in Tip #94 [http://www.vim.org/tips/tip.php?tip_id=94]. Even if I do "ctags --file-scope=no -R" in the parent directory and "ctags *.[ch]" in my sub-directory and I'm in my sub-directory, still it does not fix the problem. I even changed my tags option to 'set tags=./tags;tags;~/code'. These steps are part of the suggested solution by the ctags author, Darren Hiebert, as described in the ctags FAQ [http://ctags.sourceforge.net/faq.html#15]. I believe this is what Brett Stahlman was referring to. Jason Aeschilman
