Example:Let's say I'm working on the 7z project.
First I create a file ssipscite/plugins/searchsip_userprefs/7z_example.cfg with the contents
[main] srcdir1=C:\delldev\dev_here\ssipscite\exampleThis tells SsipScite that it can create an index of all source code in this directory. (Update this path based on where the files are).
Then, I can start ssipscite/SciTE.exe, and open 7zIn.c.
What does CSzCoderInfo refer to? I can press F12 and go to the definition:
What other files refer to this struct? I can press Ctrl-F12 and list references:
One can then click on any of the results to open that file and line.
After the index is created, these searches are noticeably faster than full-text search, and they intelligently point you to just the information you needed. Pretty useful, huh?
SsipScite works great for large codebases that cause Visual Studio to feel slow; it indexes hundreds of files a second (on my machine) and subsequent updates are fast and incremental. The code analysis is based on simple heuristics; SsipScite won't work for all coding styles.
I mainly wrote this for myself to use (and it's been very helpful over the past month), but you can Download if you'd like to try (win32, Python source).