Terminal basics · Lesson 27 of 34 · 8 minutes

Quoted paths with spaces

Use quotes so a path containing spaces remains one argument.

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 a quoted directory
Run mkdir -p "lab/quoted space".
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/quoted space"
```
Remember: Creating a folder does not change the current directory.
2
Create a file in the quoted path
Run touch "lab/quoted space/note.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/quoted space/note.txt"
```
Remember: touch is not a way to empty a file that already has content.
3
List the quoted path
Run ls "lab/quoted space".
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/quoted space"
```
Remember: A listing is not proof that you can read or modify every listed file.

Understand the pattern

Quoting paths that contain spaces helps operators explain what they know before they change anything.

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/quoted space"

(no output; exit 0)

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

$ touch "lab/quoted space/note.txt"

(no output; exit 0)

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

$ ls "lab/quoted space"

note.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 with spaces”, which interpretation is safe?A command appearing in history proves it completed successfully.A successful first check guarantees that every dependent service is healthy.touch is not a way to empty a file that already has content.

Apply it elsewhere

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

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Escaped spaces 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