testcode.git

README.md  1) # testcode
README.md  2) 
README.md  3) This is just a test project. You can do anything here, test g++, make, cmake,
README.md  4) git, cscope, and IDE projects.
README.md  5) 

README.md  6) ## Getting the project

README.md  7) 
README.md  8) You can get a copy of this project by clicking on the

README.md  9) [ZIP](http://git.dlma.com/testcode.git/zipball/main)
README.md 10) or [TAR](http://git.dlma.com/testcode.git/tarball/main) buttons

README.md 11) near the top right of the GitList web page.

README    12) 

README    13) You can clone from the origin with:
README    14) 

README.md 15)     git clone ssh://USERNAME@dlma.com/~/git/testcode.git

README    16) 

README.md 17) ## IDEs
README.md 18) 
README.md 19) ### tmux vim entr
README.md 20) 
README.md 21) Create two panes in tmux, run vim in one, and run entr in the other with a command like:
README.md 22) 
README.md 23)     find . -type f \( -name \*.[ch]pp -or -name \*.[ch] \) | \
README.md 24)     entr -c sh -c 'ctags -R *; make -j$(nproc) && valgrind --leak-check=yes product/testcode'
README.md 25) 
README.md 26) or, to compile with debug info and run in gdb:
README.md 27) 
README.md 28)     find . -type f \( -name \*.[ch]pp -or -name \*.[ch] \) | \
README.md 29)     entr -c sh -c 'ctags -R *; make debug -j$(nproc) && gdb product/testcode'
README.md 30) 
README.md 31) Tips: you can also run ctags and cscope, and in vim you can grep and use the QuickFix window with commands like...
README.md 32) 
README.md 33)     :grep -rI searchterm .
README.md 34)     :cw
README.md 35) 

README.md 36) See [this QuickFix tip for sorting results by filename](http://git.dlma.com/dotfiles.git/commit/0cb566c53caf931c8b3f423dcfded4660b220cbb).
README.md 37) 

README.md 38) #### entr One-Liner for When no Makefile
README.md 39) 
README.md 40) [This entr command is handy](https://twitter.com/dblume/status/1421011043489255424) when composing interview questions without a Makefile:
README.md 41) 

README.md 42)     ls -1 *.h *.cpp | entr sh -c 'g++ -Wall -std=c++17 -pthread *.cpp && valgrind --leak-check=yes ./a.out'

README.md 43) 

README.md 44) ### Visual Studio Code and WSL2
README.md 45) 
README.md 46) Once you've got the [Remote -WSL extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-wsl)
README.md 47) for WSL, you can invoke Code from the WSL side.
README.md 48) 
README.md 49)     code .
README.md 50) 
README.md 51) Or, if it's not in your path, something like...
README.md 52) 
README.md 53)     /mnt/c/Users/$USER/AppData/Local/Programs/Microsoft\ VS\ Code/bin/code .
README.md 54) 
README.md 55) ### Other IDEs
README.md 56) 
README.md 57) Look for the presence of their project files. They should work normally.
README.md 58) 
README.md 59) ## Current Features

README    60) 
README    61) * Multiple directories for testing build systems and IDEs
README    62) * "make" essentially works.
README    63) 

README.md 64) ## Is it any good?

README.md 65) 
README.md 66) [Yes](https://news.ycombinator.com/item?id=3067434).
README.md 67) 

README.md 68) ## To Do

README    69) 
README    70) * Compare make vs. cmake vs. autotools

README    71) * Experiment with ctags generation