Run mkdir lab so the note has a safe sandbox folder.
mkdir lab
Mission 13
Editing with nano
Open the simulated nano editor, save a text file, and verify your change.
Nano and editingnanocatstat
Lesson 13 of 360
0/360 lessons
0/17 missions
Nano and editing · 10 minutes
New learnerrank
0XP
0%complete
learner@clairos:/home/learner $
Unix ops lab: type a command, press Enter
Instructions
10 minutes
Click any instruction for the command details, the why, and the common mistake to avoid.
Run nano lab/incident-notes.txt.
nano lab/incident-notes.txt
After saving, run cat lab/incident-notes.txt.
cat lab/incident-notes.txt
Run stat lab/incident-notes.txt.
stat lab/incident-notes.txt
Save progress
Keep learning across sessions.
Create a free account to sync completed lessons, XP, streaks, course status, and your next lesson across sessions.
Checking account status...
Progress sync is idle.
0XP
New learnerrank
0day streak
0best streak
0daily streak
0lessons
0courses
0missions
0tasks
Noverified
Progress sync stores completion IDs, scores, streaks, badges, and game settings. Terminal contents, editor snippets, lab scratch, email, and real names are never published on leaderboards or share cards.
Lesson support
What to notice while you play.
Edit a lab file, save it, and verify the saved content.
The nano panel is simulated, and the save writes to local browser state.
Reading back changes is a simple habit that prevents confusion.
- Forgetting to save before closing.
- Editing a path whose parent folder does not exist.
Reference
Commands in this lesson.
nano <file>
Open a simulated nano editor.
cat <file>
Print text file contents.
stat <path>
Show lab file details.