Databases
StackOverflow2013
Postsdbo
POTagBar plugin cannot be added using ctags
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POTagBar plugin cannot be added using ctags
    text
    copied!<p>I'm trying to get the vim TagBar plugin to work with groovy language. I'm running on a Debian Linux. I've installed exhuberant-ctags.</p> <p>I've searched on the web and found those two sites:</p> <ul> <li><a href="https://github.com/majutsushi/tagbar/issues/84" rel="nofollow">https://github.com/majutsushi/tagbar/issues/84</a></li> <li><a href="https://github.com/majutsushi/tagbar/wiki#groovy" rel="nofollow">https://github.com/majutsushi/tagbar/wiki#groovy</a></li> </ul> <p>So I created a <code>~/.ctags</code> file containing</p> <pre><code>--langdef=groovy --langmap=groovy:.groovy --regex-groovy=/^[ \t][(private|public|protected) ( \t)][A-Za-z0-9&lt;&gt;]+[ \t]+([A-Za-z0-9]+)[ \t](.)[ \t]{/\1/f,function,functions/ --regex-groovy=/^[ \t]*def[ \t]+([A-Za-z0-9_]+)[ \t]\=[ \t]{/\1/f,function,functions/ --regex-groovy=/^[ \t]*private def[ \t]+([A-Za-z0-9_]+)[ \t]/\1/v,private,private variables/ --regex-groovy=/^[ \t]def[ \t]+([A-Za-z0-9_]+)[ \t]/\1/u,public,public variables/ --regex-groovy=/^[ \t][abstract ( \t)][(private|public) ( \t)]class[ \t]+([A-Za-z0-9_]+)[ \t]/\1/c,class,classes/ --regex-groovy=/^[ \t][abstract ( \t)][(private|public) ( \t)]enum[ \t]+([A-Za-z0-9_]+)[ \t]/\1/c,class,classes/ </code></pre> <p>And I've added this at the end of my .vimrc file:</p> <pre><code>let g:tagbar_type_groovy = { \ 'ctagstype' : 'groovy', \ 'kinds' : [ \ 'p:package', \ 'c:class', \ 'i:interface', \ 'f:function', \ 'v:variables', \ ] \ } </code></pre> <p>But when I restart vim and edit a file with a simple class, I don't see anything in tagbar. Just the first line "press for help".</p> <p>Does anybody knows why I can't manage to have it work?</p> <p>Thanks</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload