Skip to content

Commit 9016b17

Browse files
majutsushivim-scripts
authored andcommitted
Version 2.1
This is mostly a bug-fix release. - Make Tagbar work in (hopefully) all cases under Windows - Handle cases where 'encoding' is different from system encoding, for example on a Chinese Windows with 'encoding' set to "utf-8" (see manual for details in case it doesn't work out-of-the-box) - Fixed a bug with the handling of subtypes like "python.django" - If a session got saved with Tagbar open it now gets restored properly - Locally reset foldmethod/foldexpr in case foldexpr got set to something expensive globally - Tagbar now tries hard to go to the correct window when jumping to a tag - Explain some possible issues with the current jsctags version in the manual - Explicitly check for some possible configuration problems to be able to give better feedback - A few other small fixes
1 parent 30f506a commit 9016b17

File tree

3 files changed

+354
-80
lines changed

3 files changed

+354
-80
lines changed

doc/tagbar.txt

Lines changed: 44 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
Author: Jan Larres <jan@majutsushi.net>
44
Licence: Vim licence, see |license|
55
Homepage: http://majutsushi.github.com/tagbar/
6-
Version: 2.0.1
6+
Version: 2.1
77

88
==============================================================================
99
Contents *tagbar* *tagbar-contents*
@@ -113,6 +113,12 @@ with doctorjs/jsctags and will use that if present, other programs require
113113
some configuration (see |tagbar-extend|). If a program does not work even with
114114
correct configuration please contact me.
115115

116+
Note: jsctags has to be newer than 2011-01-06 since it needs the "-f" option
117+
to work. Also, the output of jsctags seems to be a bit unreliable at the
118+
moment (especially regarding line numbers), so if you notice some strange
119+
behaviour with it please run it manually in a terminal to check whether the
120+
bug is in jsctags or Tagbar.
121+
116122
==============================================================================
117123
2. Requirements *tagbar-requirements*
118124

@@ -417,6 +423,21 @@ Example:
417423
let g:tagbar_autoshowtag = 1
418424
<
419425

426+
*g:tagbar_systemenc*
427+
g:tagbar_systemenc~
428+
Default: value of 'encoding'
429+
430+
This variable is for cases where the character encoding of your operating
431+
system is different from the one set in Vim, i.e. the 'encoding' option. For
432+
example, if you use a Simplified Chinese Windows version that has a system
433+
encoding of "cp936", and you have set 'encoding' to "utf-8", then you would
434+
have to set this variable to "cp936".
435+
436+
Example:
437+
>
438+
let g:tagbar_systemenc = 'cp936'
439+
<
440+
420441
------------------------------------------------------------------------------
421442
HIGHLIGHT COLOURS *tagbar-highlight*
422443

@@ -486,7 +507,9 @@ complicated cases.
486507

487508
Tagbar has a flexible mechanism for extending the existing file type (i.e.
488509
language) definitions. This can be used both to change the settings of the
489-
existing types and to add completely new types.
510+
existing types and to add completely new types. A complete configuration
511+
consists of a type definition for Tagbar in your |vimrc| and optionally a
512+
language definition for ctags in case you want to add a new language.
490513

491514
Every type definition in Tagbar is a dictionary with the following keys:
492515

@@ -577,12 +600,13 @@ ctagsargs: The arguments to be passed to the filetype-specific ctags program
577600
program.
578601

579602

580-
You then have to assign this dictionary to a variable with the name
603+
You then have to assign this dictionary to a variable in your vimrc with the
604+
name
581605
>
582606
g:tagbar_type_{vim filetype}
583607
<
584608
For example, for C++ the name would be "g:tagbar_type_cpp". If you don't know
585-
the vim file type run the following command:
609+
the vim file type then run the following command:
586610
>
587611
:set filetype?
588612
<
@@ -780,6 +804,22 @@ files.
780804
==============================================================================
781805
8. History *tagbar-history*
782806

807+
2.1 (2011-05-29)
808+
- Make Tagbar work in (hopefully) all cases under Windows
809+
- Handle cases where 'encoding' is different from system encoding, for
810+
example on a Chinese Windows with 'encoding' set to "utf-8" (see manual
811+
for details in case it doesn't work out-of-the-box)
812+
- Fixed a bug with the handling of subtypes like "python.django"
813+
- If a session got saved with Tagbar open it now gets restored properly
814+
- Locally reset foldmethod/foldexpr in case foldexpr got set to something
815+
expensive globally
816+
- Tagbar now tries hard to go to the correct window when jumping to a tag
817+
- Explain some possible issues with the current jsctags version in the
818+
manual
819+
- Explicitly check for some possible configuration problems to be able to
820+
give better feedback
821+
- A few other small fixes
822+
783823
2.0.1 (2011-04-26)
784824
- Fix sorting bug when 'ignorecase' is set
785825

0 commit comments

Comments
 (0)