This is just a test c++ repo. Go ahead and break it.

dblume Tiny tweak to the ls -1 command for entr ec4d160 @ 2021-11-17 17:24:11

include	Have cscope ignore symbolic links.	2017-12-30 14:10:49
my_lib	Added some documentation for the IDEs.	2021-09-26 17:43:16
product	Added some documentation for the IDEs.	2021-09-26 17:43:16
.gitignore	Add two implementations of round_up_to_next_power_of_two	2019-01-24 20:54:16
Makefile	Minor edit to Makefile to support explicit 'all' target.	2021-11-03 23:21:53
README.md	Tiny tweak to the ls -1 command for entr	2021-11-17 17:24:11
build	first commit	2015-11-07 22:13:58
make_path_helper	first commit	2015-11-07 22:13:58
makecscope.sh	Update way to make cscope.files list. If sent to ctags, it better matches ctags default output too.	2018-01-02 18:20:39
maketags.sh	Remove unused ctags param; don't tag filenames	2017-12-31 00:57:22
testcode.code-workspace	Add a Workspace for MS Code	2021-05-29 21:37:33
testcode.sublime-project	first commit	2015-11-07 22:13:58

README.md

testcode

This is just a test project. You can do anything here, test g++, make, cmake, git, cscope, and IDE projects.

Getting the project

You can get a copy of this project by clicking on the ZIP or TAR buttons near the top right of the GitList web page.

You can clone from the origin with:

git clone ssh://USERNAME@dlma.com/~/git/testcode.git

Create two panes in tmux, run vim in one, and run entr in the other with a command like:

find . -type f \( -name \*.[ch]pp -or -name \*.[ch] \) | \
entr -c sh -c 'ctags -R *; make -j$(nproc) && valgrind --leak-check=yes product/testcode'

or, to compile with debug info and run in gdb:

find . -type f \( -name \*.[ch]pp -or -name \*.[ch] \) | \
entr -c sh -c 'ctags -R *; make debug -j$(nproc) && gdb product/testcode'

Tips: you can also run ctags and cscope, and in vim you can grep and use the QuickFix window with commands like...

:grep -rI searchterm .
:cw

This entr command is handy when composing interview questions without a Makefile:

ls -1 *.h *.cpp | entr sh -c 'g++ -Wall -std=c++14 *.cpp && valgrind --leak-check=yes ./a.out'

Once you've got the Remote -WSL extension for WSL, you can invoke Code from the WSL side.

code .

Or, if it's not in your path, something like...

/mnt/c/Users/$USER/AppData/Local/Programs/Microsoft\ VS\ Code/bin/code .

Look for the presence of their project files. They should work normally.