Nano on Mac Is Pico 5.09: 10 of 18 Nano Keys Fail

Type nano in Terminal on a current Mac and the title bar says UW PICO 5.09. On this Mac mini, running macOS 26.4.1, /usr/bin/nano is a 4-byte symlink to pico, the editor from the University of Washington's Alpine mail client. Apple made the swap in macOS 12.3 in March 2022. Michael Tsai's roundup collects the reaction, including Rachel Kroll's theory: pico is Apache-licensed and GNU nano is GPLv3, the same reason bash gave way to zsh.

The two editors look almost the same, so most people never notice. The trouble starts when you follow a nano tutorial. I took 18 keys and options from GNU nano's own cheat sheet and drove both editors through them from a script. Pico handled 8. Three of the other 10 wrote the wrong thing into the file, and none of them showed an error.

This belongs to my series on the tools macOS bundles, after update Bash on Mac, awk on Mac and update OpenSSL on Mac. Nano is the odd one out. With the others, Apple ships an old version. With nano, it ships a different program under the same name.

How I tested pico against GNU nano

The comparison binary is GNU nano 9.2, the release the nano news page dates July 31, 2026. I didn't install it. I fetched Homebrew's 1.2 MB bottle, unpacked it into a work directory, pointed its two library paths (ncurses and gettext) at the copies already on this machine, and re-signed it. That way my PATH stayed as it was.

Each test starts an editor inside a detached tmux session (80×24, TERM=xterm-256color, LANG=en_US.UTF-8, and an empty HOME so no config file leaks in). The script sends keystrokes and saves with Ctrl-O, Enter, Ctrl-X. Then it compares the file on disk with the expected bytes. The starting file is three lines: line1, line2, line3. The pass or fail comes from the saved file, not from what the screen looked like.

$ ls -l /usr/bin/nano /usr/bin/pico
lrwxr-xr-x  1 root  wheel        4 Apr  6  2026 /usr/bin/nano -> pico
-rwxr-xr-x  1 root  wheel  1441456 Apr  6  2026 /usr/bin/pico
$ /usr/bin/pico -version
Pico 5.09

The 18 results

Key or option (nano docs)	What it should do	pico 5.09 (/usr/bin/nano)	GNU nano 9.2
Ctrl-O, then Ctrl-X	Save, exit	Works	Works
Ctrl-X, Y, Enter	Exit and save changes	Works	Works
Ctrl-S	Save	Nothing; Ctrl-X then asks to save	Works
Alt-U	Undo	Nothing; typed text stays	Works
Alt-E	Redo	Nothing (no undo to redo)	Works
Ctrl-_ 3 Enter	Go to line 3	Inserted "3" and a newline into line 1	Works
Ctrl-\	Search and replace	Search and replacement text typed into the file	Works
Ctrl-W	Search	Works	Works
Ctrl-K, Ctrl-U	Cut line, paste	Works	Works
Alt-6	Copy line	Nothing	Works
Alt-A, arrows, Ctrl-K	Mark text, cut the selection	Cut the whole line	Works
Ctrl-^, arrows, Ctrl-K	Same, older binding	Works	Works
Alt-/	Jump to end of file	Nothing; cursor stays on line 1	Works
nano +3 file	Open at line 3	Works	Works
nano -B file	Keep a backup on save	Exit 1: Argument Error: unknown flag "B"	Works (writes file~)
~/.nanorc with set tabstospaces	Tab inserts 4 spaces	Ignored; literal tab saved	Works
Paste a 128-character SSH key line	Stay one line	Works	Works
Type café	UTF-8 bytes saved	Works	Works

The bold rows are the ones that matter. When pico doesn't know a key, it doesn't beep and refuse. The keys after it get typed into the buffer. A go-to-line attempt left a stray 3 at the top of the file. A search-and-replace attempt left both search terms in the text plus an a (my answer to "replace all?"). And Alt-A did nothing, so the Ctrl-K after it cut the whole first line instead of three characters. If you save and exit as most tutorials tell you to, all of that lands on disk. For ~/.zshrc or /etc/hosts that means a broken file.

The Ctrl-_ mix-up has history behind it. An Ask Different question from 2022 asks why Ctrl-/ beeps on a Mac. The accepted answer is Ctrl-_, which only works in GNU nano. In pico, go to line is Ctrl-W then Ctrl-T. I tested it and it works in both editors, because nano 9.2 brought that legacy pair back. Tutorial advice gets this wrong too: Linux Handbook's undo guide says to press Option+U on macOS. On a stock Mac that does nothing.

Command-line flags: 8 of 15 stop pico from starting

I also tried 15 flags that nano guides commonly mention. Pico rejected 8 of them (-l, -B, -i, -E, -T4, -c, -S, -Y). Each time it printed Argument Error: unknown flag, dumped its 59-line option list and exited 1. So alias nano='nano -l' for line numbers stops the editor from opening at all. Four flags happen to mean the same thing in both: -m (mouse), -w (no wrap), -k (cut from cursor) and -x (hide the help lines).

The other three flags are the trap. nano --version, nano -V and nano --help don't print anything in pico. They open the editor, so someone checking which nano they have gets a blank buffer. The pico version check is pico -version, with one dash. For a quick answer without opening anything, use ls -l "$(command -v nano)".

One warning I expected didn't hold up. Old pico advice says pico hard-wraps long lines as you type them, which would break config lines. I typed a 96-character export PATH=... line one character at a time, at 80 and 120 columns and with -r40, and also pasted it in one go. In all four runs pico saved a single line. My SSH key test also stayed on one line. On macOS's pico 5.09 I couldn't reproduce the wrap.

Getting real nano on a Mac

Homebrew's nano formula is GNU nano 9.2 and pulls in ncurses and gettext:

brew install nano
hash -r                      # zsh/bash may have cached /usr/bin/nano
type -a nano                 # /opt/homebrew/bin/nano must come first
nano --version               # should print "GNU nano, version 9.2"
export EDITOR=nano           # in ~/.zshrc, so git and crontab -e use it

That only works if /opt/homebrew/bin comes before /usr/bin in PATH, which the brew shellenv line in ~/.zprofile takes care of. The hash -r step comes from a 2018 Ask Different thread. Back then the system nano was GNU 2.0.6, and the shell kept running it after a newer one was installed. The same thing happens now with pico. I've seen this pattern before: update Git on Mac and sed's "invalid command code" are both a case of the tool you got not being the tool the docs describe.

One thing changed in 9.2: GNU nano now refuses to start when standard output isn't a terminal. I hit this by accident when my first flag run redirected stdout to a log file. Every GNU run printed Standard output is not a terminal and exited 1, while pico started normally. If a script runs nano ... > log, it will act differently after the upgrade.

If you can't install anything, learn pico's keys for the one thing that bites: there's no undo. Ctrl-U only puts back the last cut. If you make a mess, the escape is Ctrl-X, then N to discard. The old save-and-exit question on Ask Different (44 votes) is still accurate for pico: Ctrl-O to write, Ctrl-X to leave. Just don't add Ctrl-S to that habit.

FAQ

Is nano on Mac really nano?

No. Since macOS 12.3 (March 2022), /usr/bin/nano is a symlink to pico 5.09, the Alpine project's editor. Run ls -l /usr/bin/nano to see it, or check the title bar for "UW PICO". Install GNU nano with brew install nano.

How do I undo in nano on a Mac?

In the built-in editor you can't: pico has no undo, and Alt-U (Option-U) does nothing. Ctrl-U only restores the last cut text. To throw away changes, press Ctrl-X and answer N. GNU nano from Homebrew supports Alt-U undo and Alt-E redo.

How do I save in nano on a Mac?

Press Ctrl-O, then Enter to confirm the file name, then Ctrl-X to exit. Ctrl-S does not save in the built-in pico. Ctrl-X followed by Y and Enter also saves and exits.

How this was checked: every claim about pico 5.09 and GNU nano 9.2 comes from a tmux harness I ran on 2026-10-12 on a Mac mini with macOS 26.4.1 (25E253). It covered 18 key and option tests and 15 flags per editor, plus 4 wrap runs, and judged each test by the saved file's bytes. GNU nano was an unpacked Homebrew bottle, not installed. The 12.3 date and license explanation come from Michael Tsai's roundup and its sources. The nano 9.2 release date and changes come from nano-editor.org. Ask Different threads were checked through the Stack Exchange API.