nano: The Minimal, Always-There Editor

Chapter 1 placed nano at the minimal end of this course's own spectrum. This chapter covers why it's built that way on purpose — a design philosophy, not a lack of ambition.

nano's Own Design Philosophy

Unlike Vim's own modal editing, nano is non-modal — whatever you type is inserted immediately, with no separate insert/normal mode distinction to learn first. Its most visible design decision is the row of on-screen keybinding hints permanently shown at the bottom of the screen (^X Exit, ^O Write Out, and so on) — explicitly designed so a first-time user can be productive immediately, without memorizing anything in advance.

Essential Keybindings

The ^ caret shown in nano's own on-screen hints means Ctrl — ^O is Ctrl+O. This same on-screen legend is genuinely nano's own primary interface convention: the hints aren't a beginner tutorial that disappears later, they're a permanent, always-visible part of the editor.

What nano Deliberately Doesn't Have

No plugin ecosystem, no built-in language server or code completion, no project or workspace concept at all. Editing exactly one file at a time is the assumption baked directly into nano's own design — this is a deliberate scope boundary, not a missing feature waiting to be added.

When nano Is Genuinely the Right Choice

Editing a single configuration file during a remote SSH session; a quick, one-off edit where even Vim's own modal learning curve (for someone who hasn't already invested in it) would cost more time than it saves; or simply the practical reality that nano is already installed and available with zero setup on many minimal server installs and containers, where nothing heavier may even be present at all.

Hands-On Exercises