I don't know if I'll be teaching the course again, but if I wait until next year I'll forget feedback I've received. Note that more test cases have been added (if you pull the new starter code); those are for the (potential) future!
In general, search engines are your friend.
Additionally, I highly encourage you to read through man
pages/--help
for command-line tools.
Personally, these command-line documentations used to scare me, but once I overcame that fear, I found them to be extremely informative.
git clone <url> <optional target directory/path>
git status
git add <files...>
git add -u
git diff [optional commit specifier]
(by default relative to HEAD
, the most recent commit)git diff [optional commit specifier] -- <files...>
HEAD
for the latest commit) with however many (say n
) carets (^
) to refer to however many (n
) commits before it; e.g. HEAD^
for the 2nd latest commit.HEAD
) with ~<n>
to refer to <n>
to refer to <n>
commits before it; e.g. HEAD~2
for the 3rd latest commit.HEAD
)git diff --cached
git diff --cached -- <files...>
git diff <older commit> <newer commit>
git diff <older commit> <newer commit> -- <files...>
git log
git restore --staged -- <files...>
git restore -- <files...>
git commit
git commit -m "one line message"
git remote add <name> <url>
git push <name> master
tmux
tmux new -s <name>
ctrl-b d
-d
to detach other sessions)tmux attach
tmux attach -t <name>
tmux ls
ctrl-b c
n
th windowctrl-b <n>
ctrl-b w
ctrl-b %
ctrl-b "
gdb <path/to/executable>
r <args...>
r 4 ../test/lab4/collatz.c
bt
f <n>
where <n>
is the frame number obtained from the backtracep <expr>
b <function>
b <file>:<line number>