Skip to content
This repository

Vim plugin that displays tags in a window, ordered by scope

branch: master

Better mapping init, closes #203

If someone already has a function that includes "JumpToTag" in its name
then the current method of detecting whether mappings should be
initialized would fail. Use a buffer-local variable instead.
latest commit ae46cc025b
Jan Larres authored
Octocat-spinner-32 autoload Better mapping init, closes #203 April 05, 2014
Octocat-spinner-32 doc Clarify debug instructions April 04, 2014
Octocat-spinner-32 plugin Add ? as help key, closes #194 February 28, 2014
Octocat-spinner-32 syntax Version 2.6.1 January 23, 2014
Octocat-spinner-32 .gitattributes Move tests into separate repository April 24, 2013
Octocat-spinner-32 .gitignore Ignore /doc/tags May 31, 2011
Octocat-spinner-32 .info Add simple info file November 25, 2011
Octocat-spinner-32 LICENSE Add LICENSE file, closes #197 March 21, 2014
Octocat-spinner-32 README.md fix site url in README.md (com -> io) September 30, 2013
README.md

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

Something went wrong with that request. Please try again.