>>5-8,19-20
vim is a
disintegrated development environment. To really do anything with it, you need at to least
- Install cscope
- Install ctags (for .S files and other things cscope doesn't understand)
- Build vim with cscope support (every sane Linux distro's full vim package has this by default)
- Read if_cscop.txt and paste (some of) their recommended settings into your ~/.vimrc
- Write some scripts to generate tags and cscope.out (put them in the project makefile if you can)
That's my basic setup and I still ! into the shell all the time to run indent and etc.
>>21
I always tell myself that vimscript plugins for completion or gdb connectivity are just a shitty way to re-implement emacs, and that I'll just give up and switch to evil-mode if I decide I need them. I never get around to it, though - I just use screen to open another window and run gdb or whatever in that. Thus, I'm C-a'ing all over and my emacs envy persists.