What would be the workflow when using such tools like this or Source Trail? I've used cscope once while I'm testing out vim as my main text editor a bit. Nowadays I'm using the global search feature of vscode for code exploration. Combined with the available language server for each language, it seems to work well enough for me currently.
Cscope in vim to jump between caller and callee (examine relationship). See where symbols are used. Jump to global definition. Could not live without cscope!
Cscope: A developer's tool for browsing source code
11–20 of 37 posts
Re: Cscope: A developer's tool for browsing source code
#12Re: Cscope: A developer's tool for browsing source code
#13Re: Cscope: A developer's tool for browsing source code
#14Related "CodeQuery"(https://github.com/ruben2020/codequery) which uses both cscope and ctags databases (i use both for C/C++ code from within vim) and provides a GUI frontend.
Combine with "Doxygen" and "GNU cflow" (https://www.gnu.org/software/cflow/) and you get a very good view of the static structure of any codebase.
To get a Runtime view i prefer the call graph emitted by the profiler gprof.
Re: Cscope: A developer's tool for browsing source code
#15Re: Cscope: A developer's tool for browsing source code
#16Pls use VS Code.
Re: Cscope: A developer's tool for browsing source code
#17Re: Cscope: A developer's tool for browsing source code
#18Re: Cscope: A developer's tool for browsing source code
#19Earlier quoted context omitted.
Cscope in vim to jump between caller and callee (examine relationship). See where symbols are used. Jump to global definition. Could not live without cscope!
Yes this is how I use it and I love it. I think some IDEs havee similar capability but for vim users cscope is an great way to understand large code bases by quickly jumping through callchains. There's a 'Using Cscope with Vim' tutorial on the page that covers it.