Terminal basics · Lesson 12 of 34 · 8 minutes

Quoted paths

Create and list a path that contains a space.

Open the lab Course map

Mastery 0/3Run itExplain itApply it

learner@clairos:~ $

↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Your objectives

Hints are always available. Wrong turns never cost XP.

1
Create spaced folder
Run mkdir -p "lab notes".
Hint & worked example
Create a directory. -p also creates missing parent directories and accepts an existing directory.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
mkdir -p "lab notes"
```
Remember: Creating a folder does not change the current directory.
2
Create spaced file
Run touch "lab notes/quote.txt".
Hint & worked example
Create an empty file when absent, or update timestamps without truncating an existing file.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
touch "lab notes/quote.txt"
```
Remember: touch is not a way to empty a file that already has content.
3
List spaced folder
Run ls "lab notes".
Hint & worked example
List directory entries; -a includes hidden names and -l adds ownership and permission detail.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
ls "lab notes"
```
Remember: A listing is not proof that you can read or modify every listed file.

Understand the pattern

Real-world files sometimes contain spaces, especially on macOS.

mkdir: Create a directory. -p also creates missing parent directories and accepts an existing directory.
Creating a folder does not change the current directory.
touch: Create an empty file when absent, or update timestamps without truncating an existing file.
touch is not a way to empty a file that already has content.
ls: List directory entries; -a includes hidden names and -l adds ownership and permission detail.
A listing is not proof that you can read or modify every listed file.

Worked example and expected result

$ mkdir -p "lab notes"

(no output; exit 0)

Exit status: 0. The command completed successfully in the training fixture.

$ touch "lab notes/quote.txt"

(no output; exit 0)

Exit status: 0. The command completed successfully in the training fixture.

$ ls "lab notes"

quote.txt

Exit status: 0. The command completed successfully in the training fixture.

Try a variation

Repeat this workflow in the sandbox with a different scratch filename. Keep the system fixtures unchanged and compare the observed output with your expectation before moving on.

Explain it

In “Quoted paths”, which interpretation is safe?A successful first check guarantees that every dependent service is healthy.touch is not a way to empty a file that already has content.A command appearing in history proves it completed successfully.

Apply it elsewhere

Before adapting the touch workflow from “Quoted paths” to another server, what should you do?Confirm the current directory, target identity, permissions, and the installed command behavior first.Paste the training paths unchanged into production.Skip output inspection whenever the command is familiar.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Output redirection Try an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

GNU Coreutils manual · GNU Bash manual