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. You probably
README.md 22) only need the `git ls-files` for `entr`, but I provide a bash command group with
README.md 23) `find` here so I can easily copy and change it as needed.

README.md 24) 

README.md 25)     { git ls-files && find . -type f -regex '.*\.\(cfg\|local\)'; } | \

README.md 26)     entr -c sh -c 'ctags -R *; make -j$(nproc) && valgrind --leak-check=yes product/testcode'
README.md 27) 

README.md 28) `find` could also have been `find . -type f \( -name \*.cfg -or -name \*.local \)`.

README.md 29) 

README.md 30) To compile with debug info and run in gdb:

README.md 31) 

README.md 32)     ... | entr -c sh -c 'ctags -R *; make debug -j$(nproc) && gdb product/testcode'

README.md 33) 

README.md 34) Tip: In vim you can grep and use the QuickFix window with commands like...
README.md 35) 
README.md 36)     :grep -rI --exclude=tags --exclude=cscope.* --exclude-dir=obj searchterm .

README.md 37)     :cw
README.md 38) 

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

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

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

README.md 46) 

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

README    63) 
README    64) * Multiple directories for testing build systems and IDEs
README    65) * "make" essentially works.
README    66) 

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

README.md 68) 
README.md 69) [Yes](https://news.ycombinator.com/item?id=3067434).
README.md 70) 

README.md 71) ## To Do

README    72) 
README    73) * Compare make vs. cmake vs. autotools

README    74) * Experiment with ctags generation