Version 2.5

- New command :TagbarTogglePause to freeze Tagbar in its current state so you  can switch to other files while keeping the old information displayed for  reference. (Kian Ryan)- New command :TagbarCurrentTag which reports the same information as  currenttag().- New option tagbar_indent to configure the indentation depth of the tags.- New option tagbar_show_visibility to allow disabling the visibility symbols.- Files are now cached locally to avoid additional slowdowns for slow  connections. This also makes it possible to use Tagbar with files accessed  through Netrw.- Execute ctags again even if the previous run reported errors, in case it was  a parse error that has since been fixed. If the error persists, don't  display it again.- Improved window switching and Vim exit behaviours. (Techlive Zheng)- The currenttag() function now can show the prototype instead of the actual  tag, which can be useful in some cases where ctags doesn't report all the  interesting information.- The prototype shown in the tooltip or command line should now always be  complete, even if it is spread out over more than one line in the source  file.- The TagbarAccessPublic etc. highlight groups have been renamed to  TagbarVisibilityPublic etc. to keep them in line with standard terminology.  The old names are still supported.- Various smaller improvements and bugfixes.

Author: majutsushi

README.md

@@ -0,0 +1,16 @@
+# 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.com/tagbar/ for more information.
+
+
+# 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](http://ctags.sourceforge.net/) 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