I have the following configuration setting, blatantly stolen from
" use magical ; option if has('path_extra') setglobal tags-=./tags tags^=./tags; endif
I suspect what it does is remove the default
./tags entry for tags files and instead find any tags file that's in
Initially I thought that it would pick out only a single tags file, but that is not what it does. Instead it picks out EVERY tags file in
I use a script to generate a tags file for the toplevel project and use the same script to generate another one for the area I mainly work in
project ├── myfolder │ └── tags └── tags
When I'm "in" the myfolder directory, I would like to pick out just the
project/myfolder/tags file ... otherwise I have problems with duplicate entries. It also kind of defeats the purpose of having a tags file for a subfolder, which is to "narrow" the identifiers that the ctags mechanism is aware of.
I guess my question is:
- Is there a simple, well-supported way to work with "hierarchically organized" tags files?
- What kind of workflow is the magical semicolon-path feature designed to support?