Code Monkey - Have a monkey keep track of your code and your TODO's inside of it (for starters)
Use Cargo to build the code cargo build
Then Cargo to run it aswell
If you use no parameters for cargo run you will get the usage
cargo run
cm wakeup // this will initialize a new database project.db
cm eat /path/to/folder projname // this will consume a folders files into the database
cm spit // this will show the database
cm find TODO // this will search the database for TODO
cm sleep // this will kill the project.db file
cm update // this will update the project.db
And thats the order in how todo things.
First initiate a database with:
cm wakeup
then add data to your database with
cm eat /home/smurfd/Code mycode
Then you can search for as an example TODO in your code database (you can search for what you want)
cm find TODO
That could give some output :
///////
Searching for: TODO
Found in project: 1
Found in project: 2
///////
TODO found in these rows:
cs | csharp/callback.cs | // TODO Make it show the description instead, After db is put to use
cs | csharp/view.cs | // TODO get filetype and set highlight lang. after that.
pascal | FLOGGER/FLOGGER.C | See the TODO document (which should accompany this program.)
pascal | FLOGGER/MAKEFILE | README INSTALLATION TODO OPTIMIZING Makefile bubble_sort.c \
I usually run the code by something like this to fetch the output in a out.txt file if something explodes
rustup run nightly cargo run find TODO > out.txt 2>&1