|
1 day ago | |
---|---|---|
config | 1 month ago | |
documentation | 1 week ago | |
object | 1 week ago | |
scripts | 1 week ago | |
source | 1 week ago | |
.gdb_history | 1 month ago | |
.gitignore | 1 week ago | |
Makefile | 2 days ago | |
README.md | 1 day ago |
Fork of Cscope version 15.9, with various improvements, because cscope is good and shall not be forgotten. While the original's mainentence seems abandoned and as far as I can tell you need a PhD in autoconf to compile the latest version, Csope is alive and well.
<-- Tab -->
+--Version-----------------Case--+ +--------------------------------+
A |+--------------+---------------+| |+------------------------------+|
| || Input Window | Result window || || ||
| |+--------------+ || ? || ||
|| Mode Window | || ----> || Help ||
% || | || <---- || ||
|| | || ... || ||
| || | || || ||
| || | || || ||
V |+--------------+---------------+| |+------------------------------+|
+---------------------Tool Tips--+ +--------------------------------+
Csope shines at exploring stranger and obsecure code bases due to its TUI. It sometimes gets mislabeled as a code navigation tool, but the original documentation describes it best as a “code browsing tool”. Many tools can jump you to a definition or grep for patterns, but Csope is unqie in that it allows for those and many other functionalities while providing you with a very comprehansible list of all results, ready to fire up your editor at just the spot. An example of its excelence is this project. The Cscope codebase used to be a total mess, fixing it would have been a lost cause, if not for Cscope itself. Well, Csope now.
You will have to compile from source.
After you made sure you have the following (dev) libraries installed:
ncurses
GNU Readline
GNU History (should come with Readline)
Just run:
make
This will yield the executable “csope”, which you are free to do whatever with.
Hint:
cp csope /usr/bin/
The readline integratoin should be complete -please let us know if not-, except for your prompt being used, which could easily break the TUIs display.
The rl_readline_name variable will be set to “Csope”, so you may have conditional configurations in your .inputrc with the following format:
$if Csope
# <whatever>
$endif
All can be configured sucklessly under “config/colors.h”. Hopefully the comments are self evident.