Nano Editor in Linux: Beginner's Guide

Quick take: The nano editor is the easiest terminal text editor. Open a file with nano file, edit normally, then save with Ctrl+O and exit with Ctrl+X. The shortcut bar at the bottom shows the keys (^ means Ctrl).

Introduction

The nano editor is the friendliest way to edit files in the terminal, which is why it is the default on Ubuntu and many other distributions. Unlike Vim, it works the way most people expect — you just start typing — and it shows the key shortcuts along the bottom of the screen.

This guide covers opening and saving files, the essential shortcuts, searching and replacing, and the options that make nano nicer for editing config files.

Syntax

The basic syntax of the nano command is:

nano [OPTIONS] [FILE]

Common Options and Parameters

The most useful options and parameters for the nano command:

Practical Examples

Real nano commands you can run today:

# Open or create a file
nano notes.txt
# Open a system file with sudo
sudo nano /etc/hosts
# Open with line numbers shown
nano -l script.sh
# Open without line wrapping (for config files)
nano -w /etc/nginx/nginx.conf
# Open at a specific line
nano +25 app.py

Configuring nano with nanorc

nano is more capable than its simple interface suggests, and a short configuration file makes it markedly nicer for editing code and config. Settings live in ~/.nanorc for your user (or /etc/nanorc system-wide).

# ~/.nanorc
set linenumbers     # show line numbers
set tabstospaces    # insert spaces, not tabs
set tabsize 4
set constantshow    # always show the cursor position
include "/usr/share/nano/*.nanorc"  # enable syntax highlighting

That last line turns on syntax highlighting for dozens of languages and config formats, which makes spotting a misplaced bracket or quote far easier — a real upgrade for editing files like nginx.conf or YAML.

Tips and Best Practices

• The ^ in the bottom bar means the Ctrl key — so ^X is Ctrl+X to exit.
• Use -w when editing configuration files so long lines are not wrapped and accidentally broken.
• If you save a file and the program does not see the change, make sure you edited the right path — use sudo nano for files you do not own.

Final Thoughts

nano is the editor to reach for when you want to make a quick change without a learning curve. Remember just two shortcuts — Ctrl+O to save and Ctrl+X to exit — and the rest is plain typing. It is perfect for editing config files and notes; when you need more power, that is when people graduate to Vim.