Linux has two main categories of text editors for beginners: terminal-based editors you use inside the command line, and graphical editors that open in a window like any desktop application. For the terminal, nano is the most beginner-friendly option — you open a file with nano filename, edit using normal typing, and save with Ctrl+O then exit with Ctrl+X. For graphical editing, gedit (the GNOME text editor) provides a familiar interface similar to Notepad on Windows. Both are essential tools for editing configuration files, writing scripts, and working with plain text in Linux.
The Editor Every Linux User Needs
Text editing is at the heart of Linux administration and customization. Nearly everything in Linux is configured through plain text files — the network settings in /etc/.hosts, the package sources in /etc/.apt/sources.list, shell configuration in ~/.bash.rc, web server settings in /etc/.nginx/nginx.conf. Every script you write is a text file. Every configuration change you make involves editing text.
Unlike Windows, where configuration lives in graphical settings panels and a registry database, Linux exposes configuration directly as readable, editable text files. This design gives you tremendous power — you can see exactly what is configured, copy configurations between machines, automate changes with scripts, and understand exactly what your system is doing. But it also means you need a text editor.
Linux offers an overwhelming array of text editors, from the legendary (and legendarily complex) vi and Emacs to sophisticated modern editors like VS Code. For beginners, this variety can be paralyzing. This article focuses on two editors that serve new Linux users excellently: nano, the terminal-based editor that appears in almost every Linux system and is the right tool for quick configuration file edits from the command line; and gedit, the graphical editor included with GNOME desktops that feels immediately familiar to anyone who has used Notepad or a simple word processor.
By the end of this article, you will be able to confidently open, edit, save, and close files in both editors. You will understand when each is the appropriate choice, know the keyboard shortcuts that matter most, and have the foundation to move toward more powerful editors when your needs outgrow these accessible starting points.
Understanding Plain Text Files
Before diving into specific editors, understanding what a text file is — and why it matters in Linux — provides important context.
What Is Plain Text?
A plain text file contains only characters: letters, numbers, punctuation, spaces, and line breaks. There is no formatting — no bold, no font choices, no colors, no embedded images. What you see is exactly what is stored, character by character.
This simplicity is the point. Plain text files are universal — any text editor on any operating system can read them. They are transparent — you can read them without special software and understand exactly what they contain. They are version-control friendly — tools like Git can compare two versions of a text file and show exactly what changed, line by line. And they are scriptable — programs can read, modify, and create text files automatically.
Most Linux configuration files, shell scripts, program source code, HTML files, CSS files, Markdown documents, and data files in formats like CSV and JSON are all plain text.
What Text Editors Are NOT
A text editor is not a word processor. Word processors like LibreOffice Writer or Microsoft Word save files in complex binary or XML formats that embed formatting information alongside content. If you open a configuration file with a word processor and save it, the added formatting metadata will corrupt the file, making it unreadable by the system.
Never use a word processor to edit Linux configuration files. Always use a genuine text editor.
nano: The Beginner’s Terminal Text Editor
What nano Is and Why It Matters
nano is a terminal-based text editor that runs entirely within the terminal window. It has been part of Linux for decades and is installed by default on virtually every Linux distribution. When a tutorial tells you to “edit a configuration file” from the command line, nano is almost always the right tool — it is simple, immediately usable, and shows its keyboard shortcuts right on screen.
Unlike the other classic terminal editor vi/Vim — which has a steep learning curve and a mode-based interface that confuses beginners — nano works the way most people expect a text editor to work: you open a file, the cursor is immediately in the text, you type to add or change text, and keyboard shortcuts handle saving and exiting. No modes to switch between, no commands to memorize before you can start typing.
Opening a File with nano
$ nano filename.txtIf the file exists, nano opens it displaying its contents. If the file does not exist, nano opens an empty buffer — saving it will create the new file.
To open a system configuration file (which requires administrator privileges):
$ sudo nano /etc/.hostsWhen nano opens, the screen transforms:
GNU nano 7.2 /etc/.hosts
127.0.0.1 localhost
127.0.1.1 mycomputer
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
[ Read 6 lines ]
^G Help ^O Write Out ^W Where Is ^K Cut ^T Execute ^C Location
^X Exit ^R Read File ^\ Replace ^U Paste ^J Justify ^_ Go To Line
The top bar shows the nano version and the filename. The main area displays the file contents with the cursor positioned at the beginning. The bottom two rows show the most important keyboard shortcuts — this is nano’s signature feature for beginners: you never have to remember shortcuts because they are always displayed.
Understanding nano’s Shortcut Notation
The shortcuts shown at the bottom use ^ to mean the Ctrl key. So:
^Xmeans Ctrl+X^Omeans Ctrl+O^Gmeans Ctrl+G
Some actions use M- which means Alt (or Escape on some systems):
M-Umeans Alt+U (undo)
Navigating in nano
Once nano is open, moving around the file works intuitively:
Arrow keys — move the cursor one character or line at a time in any direction.
Ctrl+F / Ctrl+B — move forward or backward one character (same as right/left arrows).
Ctrl+N / Ctrl+P — move to the next or previous line (same as down/up arrows).
Ctrl+A — move to the beginning of the current line.
Ctrl+E — move to the end of the current line.
Ctrl+Y — scroll up one page (Page Up).
Ctrl+V — scroll down one page (Page Down).
Ctrl+Home or Ctrl+_ then 1,1 — go to the very beginning of the file.
Ctrl+End — go to the very end of the file.
Ctrl+_ (Ctrl+underscore) — go to a specific line number. nano prompts for the line number and column. This is useful when a program error message tells you “error on line 47” — Ctrl+_ then 47 takes you directly there.
Editing Text in nano
Editing in nano works exactly as you would expect:
Typing inserts characters at the cursor position.
Backspace deletes the character to the left of the cursor.
Delete deletes the character at the cursor position.
Enter inserts a new line at the cursor position.
Ctrl+K — cut the entire current line and place it in nano’s clipboard (“kill” in nano terminology). Pressing Ctrl+K multiple times cuts multiple consecutive lines, accumulating them all in the clipboard.
Ctrl+U — paste the cut content (from Ctrl+K) at the cursor position (“uncut”).
Alt+6 — copy the current line without cutting it (keeps it in place and puts a copy in the clipboard).
Ctrl+Shift+C / regular Ctrl+C — copy selected text (in newer nano versions that support mouse selection).
Alt+U — undo the last action (in nano 4.0 and later, which most modern systems have).
Alt+E — redo an undone action.
Searching and Replacing in nano
Ctrl+W — search (Where Is). Opens a search prompt at the bottom of the screen. Type your search term and press Enter. nano jumps to the first match and highlights it. Press Ctrl+W again and then Enter to find the next match.
Search options (press Alt+C, Alt+R, etc. at the search prompt):
- Alt+C — toggle case sensitivity
- Alt+R — toggle regular expression matching
- Alt+B — search backwards
Ctrl+\ (Ctrl+backslash) — search and replace. Prompts for a search term, then a replacement term, then asks whether to replace each occurrence individually or all at once.
Saving a File in nano
Ctrl+O — Write Out (save). nano prompts to confirm the filename at the bottom of the screen. If you are saving to the same file, just press Enter to confirm. If you want to save to a different filename (Save As), type the new name before pressing Enter.
After saving, nano displays a brief confirmation message showing how many lines were written.
Note: nano does NOT auto-save. If you close the terminal window without saving, your changes are lost. Always explicitly save with Ctrl+O before exiting.
Exiting nano
Ctrl+X — exit. If there are unsaved changes, nano asks whether to save them:
Save modified buffer?
Y Yes
N No ^C CancelPress Y to save and exit, N to exit without saving, or Ctrl+C to cancel and return to the file without exiting.
If the file requires elevated permissions (you opened it with sudo), nano handles saving correctly because the sudo session covers the entire nano process.
Opening nano at a Specific Line Number
When you know which line needs editing (from an error message, for example):
$ nano +47 /etc/.some_config.confThe +47 opens the file with the cursor positioned at line 47.
nano with Multiple Files
You can open multiple files:
$ nano file1.txt file2.txtSwitch between open files with **Alt+< ** (previous file) and Alt+> (next file).
Key nano Settings Worth Knowing
nano’s behavior can be configured through ~/.nanorc. Some useful settings to add:
# Enable syntax highlighting
include "/usr/.share/nano/*.nanorc"
# Show line numbers
set linenumbers
# Enable mouse support
set mouse
# Auto-indent new lines
set autoindent
# Use soft-wrap instead of hard-wrap
set softwrapAdd these lines to ~/.na.no.rc (create the file if it does not exist) and they apply to all future nano sessions.
nano Essential Shortcuts: Complete Reference
| Shortcut | Action |
|---|---|
| Navigation | |
| Arrow keys | Move cursor |
| Ctrl+A | Beginning of line |
| Ctrl+E | End of line |
| Ctrl+Y | Page up |
| Ctrl+V | Page down |
| Ctrl+_ | Go to line/column number |
| Editing | |
| Ctrl+K | Cut line |
| Ctrl+U | Paste |
| Alt+6 | Copy line |
| Alt+U | Undo |
| Alt+E | Redo |
| Search | |
| Ctrl+W | Search forward |
| Ctrl+\ | Search and replace |
| File Operations | |
| Ctrl+O | Save (Write Out) |
| Ctrl+X | Exit |
| Ctrl+R | Insert file at cursor |
| Information | |
| Ctrl+G | Display help |
| Ctrl+C | Show cursor position |
gedit: The Graphical Text Editor for GNOME
What gedit Is
gedit (formerly called “GNOME Text Editor,” now replaced in GNOME 42+ by a new app simply called “Text Editor”) is the graphical text editor that ships with GNOME-based desktops — the default on Ubuntu, Fedora, and many other distributions. It provides a familiar, windowed text editing experience comparable to Notepad on Windows or TextEdit on macOS, but with useful additional features like syntax highlighting, search and replace, and plugin support.
Note on naming: Ubuntu 22.04 and later ship with a new GNOME Text Editor (not gedit) as the default. It has a slightly different interface but works similarly. Fedora 41 and later also use the new editor. gedit remains widely available and can be installed separately on any distribution: sudo apt install gedit. The principles discussed here apply to both.
Opening gedit
From the applications menu: Search for “Text Editor” or “gedit” in your application launcher and click the result.
From the file manager: Right-click on any text file and choose “Open With Text Editor” or “Open With gedit.”
From the terminal:
$ gedit filename.txt &The & runs gedit in the background, returning the terminal prompt immediately. Without &, your terminal is occupied until you close gedit.
Opening a system file with elevated privileges: Graphical editors should generally not be run with sudo directly. Instead, use the terminal to copy the file, edit it as a regular file, then copy it back — or use sudoedit which handles this safely:
$ sudoedit /etc/.hostssudoedit opens the file in your default editor with proper privilege handling. Alternatively, use nano for system file editing from the terminal.
The gedit Interface
gedit’s interface is clean and immediately familiar:
Menu bar / Header bar — contains File, Edit, View, Search, and Tools menus (in older versions) or a streamlined header with key actions (in newer GNOME style).
Tab bar — each open file appears as a tab, allowing multiple files open simultaneously. Click tabs to switch between files. Ctrl+Tab cycles through open tabs.
Editor area — the main text editing area. Click to place the cursor, then type normally.
Status bar — shows the cursor’s current line and column position, the file’s character encoding (typically UTF-8), and the line ending format (Unix/LF, Windows/CRLF, or Mac/CR).
Basic Editing in gedit
gedit uses standard graphical text editing conventions:
Typing inserts text at the cursor. Click anywhere to reposition the cursor.
Selection — click and drag to select text. Double-click to select a word. Triple-click to select a line. Ctrl+A selects all text.
Copy/Cut/Paste — standard Ctrl+C, Ctrl+X, Ctrl+V keyboard shortcuts or use the Edit menu.
Undo/Redo — Ctrl+Z to undo, Ctrl+Shift+Z to redo. Multiple levels of undo are supported.
Delete — Backspace deletes before the cursor; Delete deletes after the cursor. Ctrl+Backspace deletes the previous word; Ctrl+Delete deletes the next word.
Saving Files in gedit
Ctrl+S — Save. Saves to the current filename. If the file is new (has never been saved), opens a “Save As” dialog.
Ctrl+Shift+S — Save As. Opens a dialog to save the file with a new name or in a new location.
gedit shows unsaved changes with a dot or asterisk in the tab title, visually indicating you have modifications not yet saved.
Auto-save: gedit can be configured to automatically save files. In Preferences (Edit → Preferences or the application menu), enable “Autosave files every X minutes.” This is a safety net but does not replace explicit saving before closing.
Finding and Replacing in gedit
Ctrl+F — Find. Opens the find bar at the bottom of the editor. Type your search term; gedit highlights all matches and navigates to the first one. Press Enter or F3 to find the next match; Shift+F3 for the previous match.
The find bar offers additional options:
- Match case checkbox — enables case-sensitive searching
- Match whole word checkbox — only matches complete words, not substrings
Ctrl+H — Find and Replace. Opens a dialog with separate search and replacement fields. You can replace one occurrence at a time or replace all occurrences simultaneously.
Ctrl+G — Go to Line. Opens a prompt to jump to a specific line number — useful when an error message references a line number.
Syntax Highlighting
One of gedit’s most useful features is syntax highlighting — it colorizes different parts of code or configuration files based on their meaning. Keywords in Python appear one color, strings another, comments a third. This makes code dramatically easier to read and errors easier to spot.
gedit automatically detects file types from their extensions and applies the appropriate highlighting. Open script.py and you get Python highlighting. Open nginx.conf and you get nginx configuration highlighting. Open style.css and you get CSS highlighting.
If gedit does not automatically detect the correct type, you can set it manually: in the status bar at the bottom, click on the language indicator (shows “Plain Text” or the current language) and select the correct type from the list.
Multiple Files and Tabs
gedit supports multiple open files through a tab interface, similar to web browsers:
Ctrl+T — open a new empty tab.
Ctrl+O — open an existing file (opens in a new tab).
Ctrl+W — close the current tab.
Ctrl+Tab / Ctrl+Alt+Page Down — switch to the next tab.
Ctrl+Shift+Tab / Ctrl+Alt+Page Up — switch to the previous tab.
The Side Panel and File Browser
gedit’s optional side panel (View → Side Panel, or F9) includes a file browser that allows navigating the filesystem and opening files without returning to the file manager. For editing multiple files in a project directory, keeping the side panel open is a useful workflow.
gedit Plugins
gedit supports plugins that extend its capabilities. Access them through Edit → Preferences → Plugins (or the equivalent in newer versions):
Spell Checker — checks spelling as you type or on demand. Useful for writing documentation and prose.
Sort — sorts selected lines alphabetically. Practical for organizing configuration lists.
External Tools — lets you define custom commands that process the current file through external programs.
Git — shows git status information for files in version-controlled directories.
Code Comment — toggle comments in code files with a keyboard shortcut.
Enable the plugins you find useful; most are lightweight and add genuine value.
gedit Essential Shortcuts: Complete Reference
| Shortcut | Action |
|---|---|
| File Operations | |
| Ctrl+N | New file |
| Ctrl+O | Open file |
| Ctrl+S | Save |
| Ctrl+Shift+S | Save As |
| Ctrl+W | Close tab |
| Ctrl+Q | Quit gedit |
| Editing | |
| Ctrl+Z | Undo |
| Ctrl+Shift+Z | Redo |
| Ctrl+X | Cut |
| Ctrl+C | Copy |
| Ctrl+V | Paste |
| Ctrl+A | Select all |
| Navigation | |
| Ctrl+G | Go to line |
| Ctrl+Tab | Next tab |
| Ctrl+Shift+Tab | Previous tab |
| F9 | Toggle side panel |
| Search | |
| Ctrl+F | Find |
| Ctrl+H | Find and Replace |
| F3 | Find next |
| Shift+F3 | Find previous |
| View | |
| Ctrl++ | Increase font size |
| Ctrl+- | Decrease font size |
| Ctrl+0 | Reset font size |
nano vs. gedit: Choosing the Right Editor
Both nano and gedit are excellent tools for different situations. Understanding when to reach for each prevents frustration.
Use nano When:
You are already in the terminal. If you are running commands in a terminal and need to quickly edit a file, opening nano in that same terminal is faster than switching to a graphical editor.
You are working on a remote server. Remote server management is done through SSH — a terminal connection. There is no graphical desktop available. nano (or another terminal editor) is your only option.
You are editing a system configuration file with sudo. Using sudo nano /etc/.file is the standard, safe pattern for privilege-required file editing from the terminal. Running a graphical editor with sudo is generally not recommended.
The file is small and the edit is simple. Adding a line to /etc/.hosts, changing a setting in a config file, or making a quick fix to a script — nano’s quick open-edit-save-exit workflow is ideal for these.
You are in a minimal environment (a recovery shell, a container, a headless server). nano is nearly always available even in minimal installations.
Use gedit (or your graphical editor) When:
You are working with longer files. The graphical interface with scrollbars, mouse navigation, and visible line numbers makes working with longer documents more comfortable than the terminal.
You are writing or editing code in a project. The file browser side panel, tab support, and syntax highlighting make gedit practical for multi-file project editing, though a full IDE or editor like VS Code may eventually serve this need better.
You need visual comfort. Adjustable font size, full mouse support, visual syntax highlighting, and a familiar windowed interface reduce cognitive friction for users not yet accustomed to terminal editing.
You are editing a personal file in your home directory. Configuration files in ~/.bash.rc, ~/.con.fig/, or personal scripts that do not require sudo are well-suited to graphical editing.
You want undo history beyond the session. gedit maintains undo history for the life of the file’s open session; nano’s undo works within the current session but with more limited history in older versions.
The Practical Answer for Most Beginners
Use nano for system files and command-line workflows. Use gedit for personal files and longer editing sessions. Both skills are worth developing — there will be situations where only one is available or appropriate.
Other Text Editors Worth Knowing About
While nano and gedit serve beginners well, knowing what else exists prepares you for when your needs grow.
Vim / Vi
Vi is the original Unix text editor, available on virtually every Unix-like system ever created. Vim (Vi Improved) extends it with many additional features. The catch: Vim uses a modal interface where you switch between “Normal mode” (for navigating and issuing commands) and “Insert mode” (for typing text). This modal design confuses beginners initially but ultimately enables very efficient editing for those who invest in learning it.
On almost every Linux system, pressing Escape then :q! exits Vim without saving — essential knowledge for when you accidentally open it and need to escape.
Vim is worth learning if you manage many servers or write code extensively. The investment pays off through powerful text manipulation capabilities.
Emacs
Emacs is the other legendary Unix editor — the great rival to Vim in decades of “editor wars.” Emacs is more like an entire computing environment than just a text editor: it includes an email client, news reader, calendar, games, and an extensible Lisp programming environment. It is extraordinarily powerful but has an even steeper learning curve than Vim.
Visual Studio Code
VS Code is a modern, graphical code editor from Microsoft that has become the most popular editor for software development across all platforms including Linux. It offers excellent syntax highlighting, git integration, debugging support, and a massive extension ecosystem. For anyone who writes code, VS Code is worth installing: sudo snap install code --classic or from code.visualstudio.com.
Kate / KWrite
Kate and KWrite are KDE text editors — Kate being a full-featured code editor, KWrite a simpler document-oriented editor. If you use KDE Plasma as your desktop, these integrate naturally with the desktop environment and are excellent alternatives to gedit.
Mousepad
The XFCE default text editor, Mousepad, is a lightweight graphical editor similar to gedit but more minimal. It is the right choice for XFCE desktop users wanting a graphical editor without installing GNOME dependencies.
Practical Exercises: Building Confidence with Both Editors
The fastest way to become comfortable with nano and gedit is hands-on practice. Here are guided exercises for each.
Exercise 1: Edit Your Shell Configuration with nano
$ nano ~/.bash.rcNavigate to the end of the file (Ctrl+End). Add a new line:
bash
# My custom alias
alias ll='ls -la'Save with Ctrl+O, press Enter to confirm, then exit with Ctrl+X.
Apply the change:
$ source ~/.bash.rcTest that your alias works:
$ llExercise 2: Search and Replace in nano
Create a practice file:
$ nano practice.txtType several lines containing the word “color” (use American spelling). Then use Ctrl+\ (search and replace) to replace all occurrences of “color” with “colour” (British spelling). Practice replacing one at a time (press Y for each match) and then all at once (press A when prompted).
Exercise 3: Open and Edit with gedit
Open gedit from the applications menu. Create a new file (Ctrl+N). Write a short list of tasks — anything you like. Use Ctrl+H (Find and Replace) to replace one word throughout the document. Save the file to your Documents folder with Ctrl+Shift+S. Close the tab with Ctrl+W.
Exercise 4: Edit a System File with sudo nano
View the current contents of your hosts file:
$ cat /etc/.hostsOpen it for editing (read-only practice — we will not actually change it):
$ sudo nano /etc/.hostsNavigate around the file. Notice that nano shows [Modified] if you accidentally press any key that changes content. Press Alt+U to undo any accidental changes. Exit with Ctrl+X without saving.
Conclusion: Two Tools for Every Situation
nano and gedit together cover the full range of text editing needs most Linux beginners encounter. nano’s presence in nearly every terminal environment and its always-visible keyboard shortcuts make it the indispensable tool for command-line file editing — no other editor is as accessible to someone new to the terminal. gedit’s familiar graphical interface, syntax highlighting, and tab support make it comfortable for longer editing sessions and multi-file work.
Mastering both editors — and developing the judgment to know which to reach for in each situation — is a foundational Linux skill that you will use throughout your Linux journey. System administrators reach for nano constantly during server configuration and troubleshooting. Developers use graphical editors for daily coding work. Home users edit configuration files with nano and write personal documents with their graphical editor of choice.
As your comfort with the terminal grows, you may find yourself gravitating toward more powerful editors: Vim for its modal efficiency, VS Code for its rich development features, or Emacs for its extensibility. But nano and gedit will remain in your toolkit long after you have mastered those tools — because sometimes the right answer is the simplest one that gets the job done.
