You can’t! I looked through the source code (thanks to apt-get source). There are no checks for lines to ignore. The relevant code is in parseFileOptions() in options.c But sometimes comments are a neccessity, so as a workaround I put a comment in as a regexp, in such as way that it is unlikely to … Read more
Like the others had said: DoctorJS (formerly jsctags) is the best option. However, integrating it with Vim by writing custom wrappers or using Vim-taglist-plus plugin, which isn’t currently working, aren’t good solutions. The easiest way I’ve found is to install the TagBar Vim plugin (NOTE: It’s TagBar, not the old infamous TagList!). See my other … Read more
Similar to this and this, the problem is you’re not running Exuberant Ctags, you’re running GNU Emacs etags, which also provides a ctags executable. Run ctags –version and you’ll see something like this: ctags (GNU Emacs 23.1) Copyright (C) 2009 Free Software Foundation, Inc. This program is distributed under the terms in ETAGS.README And if … Read more
Further to Blixtor’s answer, you’ll need to think a little carefully about the design of the script. I’d recommend segregating the design such that the autocommand uses the Windows “start” command or similar to run an external script in the background: thereby preventing Vim from being unresponsive while the tag file is generated. That script … Read more
Yes, you should tell Vim where to find your tags file with something like: :set tags=/path/to/tags This is not very optimal, though. This line in your ~/.vimrc should help: set tags=./tags,tags;$HOME It tells Vim to look for a tags file in the directory of the current file, in the current directory and up and up … Read more
I’ve spent quite some time struggling with this myself. The closest I ever got was something called gccsense. Unfortunately, the project seems abandoned and moreover it was difficult setting it up because English was not the author’s first language. I ended up approaching the problem from another angle. I made the decision that intellisense/autocomplete was … Read more
Install Homebrew, then do: brew install ctags
I think that the easiest way is to use “g ctrl-]” instead of just “ctrl-]”. If there is only one match, it will take you there. If there are multiple matches, it will list them all, letting you choose the one you want, just like :tselect. The best of both worlds. 🙂
au BufWritePost *.c,*.cpp,*.h silent! !ctags -R & The downside is that you won’t have a useful tags file until it completes. As long as you’re on a *nix system it should be ok to do multiple writes before the previous ctags has completed, but you should test that. On a Windows system it won’t put … Read more
The –exclude option does not expect a list of files. According to ctags‘s man page, “This option may be specified as many times as desired.” So, it’s like this: ctags -R –exclude=.git –exclude=node_modules –exclude=test