Apply for the next session

Lesson Intro

OK! So, there’s more stuff. Yep. More things.

Now that we’ve talked about all the ‘clicky’ Graphical User Interface stuff in extreme detail, let’s explore the “Command Line.”

The Goals

  1. OH YEAH...

    More about the Finder settings! Set the sidebar and some general finder preferences.

  2. Zoom in and out with - basically everything

    (it’s: command &   or +) Try it!

  3. Understand "file paths"

    How the system organizes files with “paths”

  4. Intro to "Terminal"

    Some computers don’t have “graphical user interfaces” and so you use the command line.  Serious HACKERS session.

"SPACES" recap

In the future, it’s likely that you will have some “utility” type apps or helpers that you need around. Confine them to a ‘space’ and keep them available…  but out of the way. This may be a “Terminal Window” or an email client or some webpage you are trying to keep open for communication.

Mission control (spaces) options

When the spaces automatically move based on recent use, it can be confusing. Check out these options.

Application bar

Each application is unique… BUT they also share some similar bits. They all have “Files.” Those files can usually be “Edited. You have to “View” them. You’ll need to view them in the “Window” that the OS provides. And you’ll probably need “Help” sometimes. (“Go?” Who knows… Apple)

Sometimes there’s a “Format” or who knows what… but – there’s a pattern. The “Application bar” has some common logic to it. You can count on it.


There are “Tabs” like you may be used to in the browser… but in the finder – they seem pretty useless. What do you think?

The file path

You can “see” it in many ways. At the core, it’s just some organization. There’s plenty of file types and places to keep them.

Your “home” folder is your Username.

Macintosh Hard Drive / Users / YourUserName

That is the “Root” folder for you.

Having a short computer name – and username can make things a bit easier.


Before Graphical user interfaces, we had things like Microsoft Disk Operating System.

This terminal is a similar experience.

(note that MS uses a “backslash”  \   and Mac uses a “forward slash”  / )


Those giant “server” computer facilities don’t have a mouse.

Here’s a start with how to move around the file system with “terminal.” (or “The Command Line”)

Print Working Directory: pwd

Change Directory: cd (needs a file-path/too)

List Files List Files: ls

Make Directory: mkdir

touch (needs a file-name.extension): creates a file

nano (needs the file name) (details)

What else???

cd ~/ (gets you back to the “root” folder) (also just cd does that?)

cd ~/a/b/c

Terminal will need permission to use your files

This is a newer security feature for Mac. Now it asks you to explicitly give each program permission to use your files. Because if they didn’t then Mark would try and look at your photos.

You might not see the window pop up – or close it by accident. So, if your terminal isn’t able to access your files – then this is why! This is a good thing to think about for any application that isn’t working.

Today's Exercises:

  1. Practice navigating the file system with Terminal

    The regular terminal is fine. But for some reason, I use iTerm 2.

    30 minutes suggested
  2. Markup a few famous websites

    Find a few “famous” websites and draw some boxes on your favorite features.

    30 minutes suggested
  3. Try "zooming" in and out

    Test it in a bunch of different applications and situations. If you have a trackpad, you can spread your fingers out across it and “pinch” to zoom in and out in many situations.

    10 minutes suggested
  4. Any hidden files?

    Check your “user” (home) folder for any hidden files.

    5 minutes suggested
Apply for the next session