Mod 0 Session 2 Practice Tasks

mod_0_session_2_practice_tasks.md

Session 2 Practice Tasks

The assignments listed here should take you approximately 55 total minutes.

To start this assignment, click the button in the upper right-hand corner that says Fork. This is now your copy of the document. Click the Edit button when you're ready to start adding your answers. To save your work, click the green button in the bottom right-hand corner. You can always come back and re-edit your gist.

1. Creating Files and Directories (10 min)

Need help? You can go back to the files/directories portion of the lesson here.

Scroll down to the bottom of this page and look at the image of the directories and files. Use commands in your terminal to create the directories and files structured exactly how they appear in the image.

When you're done, type history to see your commands. Copy and paste the commands that were used to create the directory and files:

 110  ls
  111  mkdir session_3_practice
  112  cd session_3_practice
  113  touch budget.csv
  114  touch mentors.txt
  115  mkdir notes
  116  mkdir practice
  117  cd notes
  118  touch git_notes.txt
  119  touch command_line_notes.txt
  120  cd ..
  121  cd practice
  122  touch git_practice.txt
  123  mkdir projects
  124  cd projects
  125  touch game.js

Since this is just a practice directory, feel free to remove the parent directory session_3_practice when you're done with this exercise.

2. Git Practice (15 min)

You can reference the files/directories portion of the lesson here.

Follow the steps below to practice the git workflow. Be ready to copy-paste your terminal output as confirmation of your practice.

1. Create a directory called git_homework. Inside of there, create a file called quotes.txt.
2. Initialize the directory
3. Check the git status
4. Add your quotes.txt file to the staging area
5. Check the git status
6. Create an initial commit
7. Check the status
8. Add your favorite quote to the quotes.txt file
9. Check the status
10. Check the diff
11. Add the changes to the staging area
12. Commit the new changes
13. Check the status
14. Show the log in oneline (yes, oneline, not a spelling error) format

Copy and paste all of the terminal text from this process below (not just the history):

cameronmackintosh@Camerons-MacBook-Pro ~ % mkdir git_homework
cameronmackintosh@Camerons-MacBook-Pro ~ % cd git_homework
cameronmackintosh@Camerons-MacBook-Pro git_homework % touch quotes.txt
cameronmackintosh@Camerons-MacBook-Pro git_homework % git init
Initialized empty Git repository in /Users/cameronmackintosh/git_homework/.git/
cameronmackintosh@Camerons-MacBook-Pro git_homework % git status
On branch master

No commits yet

Untracked files:
  (use "git add <file>..." to include in what will be committed)
	quotes.txt

nothing added to commit but untracked files present (use "git add" to track)
cameronmackintosh@Camerons-MacBook-Pro git_homework % git add quotes.txt
cameronmackintosh@Camerons-MacBook-Pro git_homework % git status
On branch master

No commits yet

Changes to be committed:
  (use "git rm --cached <file>..." to unstage)
	new file:   quotes.txt

cameronmackintosh@Camerons-MacBook-Pro git_homework % git commit -m "initial commit"
[master (root-commit) 386722d] initial commit
 1 file changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 quotes.txt
cameronmackintosh@Camerons-MacBook-Pro git_homework % git status
On branch master
nothing to commit, working tree clean
cameronmackintosh@Camerons-MacBook-Pro git_homework % echo "The man who never made a mistake never made anything." >> quotes.txt
cameronmackintosh@Camerons-MacBook-Pro git_homework % cat quotes.txt
The man who never made a mistake never made anything.
cameronmackintosh@Camerons-MacBook-Pro git_homework % git status
On branch master
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
	modified:   quotes.txt

no changes added to commit (use "git add" and/or "git commit -a")
cameronmackintosh@Camerons-MacBook-Pro git_homework % git diff quotes.txt
diff --git a/quotes.txt b/quotes.txt
index e69de29..6b393e2 100644
--- a/quotes.txt
+++ b/quotes.txt
@@ -0,0 +1 @@
+The man who never made a mistake never made anything.
cameronmackintosh@Camerons-MacBook-Pro git_homework % git add quotes.txt
cameronmackintosh@Camerons-MacBook-Pro git_homework % git commit -m "second commit"
[master 3904b50] second commit
 1 file changed, 1 insertion(+)
cameronmackintosh@Camerons-MacBook-Pro git_homework % git status
On branch master
nothing to commit, working tree clean
cameronmackintosh@Camerons-MacBook-Pro git_homework % oneline 
zsh: command not found: oneline
cameronmackintosh@Camerons-MacBook-Pro git_homework % git log
commit 3904b50bc3923eabcd81ec0165717294a22da87f (HEAD -> master)
Author: Cameron Mackintosh <cbmackintosh@outlook.com>
Date:   Wed Oct 7 17:24:34 2020 -0600

    second commit

commit 386722dbd75285bfa75d81958f3a48e858f5d0be
Author: Cameron Mackintosh <cbmackintosh@outlook.com>
Date:   Wed Oct 7 17:20:07 2020 -0600

    initial commit
cameronmackintosh@Camerons-MacBook-Pro git_homework % 

IMPORTANT: Do not remove this git_homework directory. You will be using this directory during Thursday's session.

3. Classes, Attributes, and Methods (15 min)

Look at the template below for a CardboardBox class. Fill in missing blanks with additional attributes and methods.

Class: CardboardBox

Attributes:

• width (integer)
• depth (integer)
• height (integer)
• thickness (float)

Methods:

• break_down
• stack
• use_as_sled
• store_items

4. Modify your Zsh Prompt (10 min)

• Make sure that your shell is set to zsh by running the following command: $ chsh -s /bin/zsh. Remember to omit the $! Note that macOS Catalina and later operating systems already use zsh as the default shell.

• Watch this video and follow each step to modify your own zshrc configuration file. As mentioned in the video, you will need this snippet below:

# Load version control information
autoload -Uz vcs_info
precmd() { vcs_info }

# Format the vcs_info_msg_0_ variable
zstyle ':vcs_info:git:*' formats '%b'

# Determine if current working directory is a git repository
git_branch_color() {
  if current_git_status=$(git status 2> /dev/null); then
    parse_git_dirty
  else
    echo ""
  fi
}

# Change branch color if working tree is clean
parse_git_dirty() {
  if current_git_status=$(git status | grep 'Changes to be committed:\|Untracked files:\|modified:|deleted:' 2> /dev/null); then
    echo "%F{red}"
  else
    echo "%F{green}"
  fi
}

# Set up the prompt (with git branch name)
setopt PROMPT_SUBST
PROMPT='%F{white}%d $(git_branch_color)${vcs_info_msg_0_} %f$'

5. Questions/Comments/Confusions

If you have any questions, comments, or confusions that you would like an instructor to address, list them below:

1. When I initially entered the command atom ~/.zshrc I was getting the error message "zsh: command not found: atom" I worked around this by accessing Atom through the GUI and creating a new file called .zshrc. Then when I returned to the terminal and entered the command atom ~/.zshrc it opened up the Atom file I had just created. That's where I copy/pasted the code snippet for Step 4. Is that okay?

Extensions

1. This course is how I personally learned command line. If time permits, I highly recommend reading and practicing.

2. Also recommended by Jeff Casimir: Michael Hartl's Learn Enough Command Line.

z_img_1.png

@cbmackintosh
I believe you entered that command correctly. A quick way to get that command is to bring up the Atom menu, and select Install Shell Commands if you encounter that in the future.

Nice work here! You'll get more practice using the terminal and making commits as you complete your Turing prework. Remember- you’ll never use ls too much! I'd highly recommend a little research on ‘tab complete’ if you aren't using tab to auto-complete file and directory names in your terminal- familiarizing yourself with this early on makes life much easier.