Finding your way in vim: tags, cscope, grep and more

&#62; A word of caution first: there is no perfect symbol-based navigation for programming languages such as C++ or Java in vim, as vim doesn't perform any syntax analysis of the code.<p>At least for Python, Vim's OmniCompletion does a reasonable job of figuring out function names:<p><a href="http://vimdoc.sourceforge.net/htmldoc/version7.html#new-omni-completion" rel="nofollow">http://vimdoc.sourceforge.net/htmldoc/version7.html#new-omni...</a>

Maybe somebody could help me to figure out how to save files properly with vim.<p>I made a script that opens all the files I need. I call the script with: :source scriptname.<p>Only problem is that the script works only if I open vim with 'vim' and not with 'sudo vim' (by the way, why is that?).<p>But if I open with 'vim', then it give me problem when I try to save...

tags and cscope look excellent.<p>However, for the grepping and general file searching stuff, wouldn't that be better done from the shell? I generally have both vim (either MacVim, or shell-vim) running, as well as a the command line sitting in a window right next to it.<p>What's the advantage of doing the searching inside vs. outside vim?

Using cscope, ctags and grep with Vim's location list and quickfix list has been a huge productivity booster for me. I highly recommend experimenting with different key bindings to ease navigating with tags other search results (:cnext :cprev :lnext :lprev, etc).

I find VIM so difficult to get my head around. Emacs seems to make more sense.. is there any point in trying to grok VIM?