Vim plugin that displays tags in a window, ordered by scope
Go to file
Jan Larres ca1c9ee2e2 Add mapping to toggle autoclose option
The current tagbar_autoclose state will be displayed in the statusline.
Also change the "hide nonpublic" flag to "v" to match the mapping and
properly document the statusline flags.
2014-06-25 17:52:43 +12:00
autoload Add mapping to toggle autoclose option 2014-06-25 17:52:43 +12:00
doc Add mapping to toggle autoclose option 2014-06-25 17:52:43 +12:00
plugin Add mapping to toggle autoclose option 2014-06-25 17:52:43 +12:00
syntax Version 2.6.1 2014-01-23 23:17:00 +13:00
.gitattributes Move tests into separate repository 2013-04-24 15:57:22 +12:00
.gitignore Ignore /doc/tags 2011-05-31 16:45:27 -03:00
.info Add simple info file 2011-11-25 22:48:02 +13:00
LICENSE Add LICENSE file, closes #197 2014-03-21 13:54:30 +13:00
README.md fix site url in README.md (com -> io) 2013-09-30 09:10:29 +02:00

Overview

Tagbar is a vim plugin for browsing the tags of source code files.
It provides a sidebar that displays the ctags-generated tags of the current file, ordered by their scope. This means that for example methods in C++ are displayed under the class they are defined in.

Check out the homepage at http://majutsushi.github.io/tagbar/ for more information.

Support for additional filetypes

For filetypes that are not supported by Exuberant Ctags check out the wiki to see whether other projects offer support for them and how to use them. Please add any other projects/configurations that you find or create yourself so that others can benefit from them, too.

Important: If the file structure is displayed wrong

If you notice that there are some errors in the way your file's structure is displayed in Tagbar, please make sure that the bug is actually in Tagbar before you report a bug. Since Tagbar uses exuberant-ctags and compatible programs to do the actual file parsing, it is likely that the bug is actually in one of those programs instead.

There is an example in :h tagbar-issues about how to run ctags manually so you can determine where the bug actually is. If the bug is actually in ctags, please report it on their website instead, as there is nothing I can do about it in Tagbar. Thank you!

You can also have a look at ctags bugs that have previously been filed on Tagbar here:
https://github.com/majutsushi/tagbar/issues?labels=ctags-bug&page=1&state=closed