##Log into :
Keys Pressed: <up> <enter>
<up and <enter> was a faster and more convenient way to log into ieng6 as that command was previously used.
##Clone your fork of the repository from your Github account (using the SSH URL):
Keys Pressed: <ctrl> r g <enter>
<ctrl r is a fast way to search through the command line recursively in the command history.
##Run the tests, demonstrating that they fail
Keys Pressed: <up> <up> <up> <enter> The javac -cp .:lib/hamcrest-core-1.3.jar:lib/junit-4.13.2.jar *.java command was 3 up in the search history, so I used the up arrow to access it.
Keys Pressed: <up> <up> <up> <up> <enter> Then the java -cp .:lib/hamcrest-core-1.3.jar:lib/junit-4.13.2.jar org.junit.runner.JUnitCore ... command was 4 up in search history, so I accessed it the same way
##Edit the code file to fix the failing test
Keys Pressed: vim <shift> L <tab> . <tab> 43 j e r 2 <shift> : w q <enter>
We need to use vim on the specific file we want to edit and the one we are going to edit is ListExamples.java. We can type vim followed by L and then a <tab> to finish the rest of the file name and a . and then another <tab> to finish the .java part.
##Run the tests, demonstrating that they now succeed
Keys Pressed: bash t <tab> <enter>
I entered bash and then t followed by a <tab> to quickly fill in the rest of the file name and then <enter>.
##Commit and push the resulting change to your Github account (you can pick any commit message!)
Keys Presesd: <ctrl> r g i t c o <enter> g i t p <enter>
I used <ctrl> r to recursively search through the command history to find git commit and git push. I didn't have to type out the whole thing as the rest of the command would appear. I then pressed <enter> following the git commands.