As a Vim user, the comparisons to Ctags and cscope were informative.
And the list of supported languages is impressive! Awk, Dos batch, COBOL, C, C++, C#, Erlang, Fortran, Java, JavaScript, Lisp, Lua, Pascal, Perl, PHP, Python, Ruby, Matlab, OCaml, Scheme, Tcl, TeX, Verilog, Vhdl and Vim.
The fancy language support is provided by exuberant ctags, so look into that if that excites you. As for cscope, GNU global is very similar; it's a bit slower for some things and a bit faster for others. Global can only find references, not callers/callees like cscope can. And the Debian maintainer of GNU Global thinks that the GNU Global maintainer is an idiot, and a consequence of this is that on Debian and derived distros the GNU Global package is ancient. But cscope is so similar, it doesn't really matter. Oh, and the gtags-cscope frontend global gives you is pretty much compatible with cscope, so any frontend that uses cscope will just work with gtags-cscope.
Heh? That post says its show-me-where-foo-is-defined functionality is broken sometimes, but it doesn't show it (and presumably they never filed a bug upstream either). I compared the two at some point last year, and they did produce slightly different results, with cscope being slightly more correct about something, but I don't recall exactly; they were VERY similar.
But GNU Global is being maintained, while cscope was abandoned. With GNU Global, you can actually update your database without recreating your tag database again. This is very useful for editor integration when you finish editing a file and save it.
As a Vim user, the comparisons to Ctags and cscope were informative.
And the list of supported languages is impressive! Awk, Dos batch, COBOL, C, C++, C#, Erlang, Fortran, Java, JavaScript, Lisp, Lua, Pascal, Perl, PHP, Python, Ruby, Matlab, OCaml, Scheme, Tcl, TeX, Verilog, Vhdl and Vim.