Linux online course

gedit Text Editor on Linux

Learn what gedit is, how to open files with it on Linux, and how to use tabs, editing tools, search and replace, syntax highlighting, spell checking, plugins, and printing.

What Is gedit?

gedit is a general-purpose graphical text editor for Linux. A text editor creates and modifies text files through a graphical interface rather than requiring command-line editing.

gedit is closely associated with GNOME, a Linux desktop environment. It has commonly served as the default or readily available editor in GNOME-oriented installations, although the exact application included depends on the Linux distribution and its version.

gedit works with plain text: text stored without word-processor features such as page layouts, embedded fonts, or rich styling. It is suitable for notes, source code, shell scripts, configuration files, and other text-based documents.

For related background, see GNOME desktop environment if available in your learning materials, and review file structure in Linux for paths and directories.

Opening gedit and Files

Start gedit from the desktop

1. Open the Linux application launcher.
2. Search for gedit or Text Editor, depending on how the distribution labels it.
3. Select the application to open a new document window.

Start gedit from a terminal

Open a terminal and run:

gedit

To open a particular file, provide its name or path as an argument:

gedit FILE_NAME

For example:

gedit notes.txt
gedit /home/alex/Documents/plan.txt

You can first change to the relevant directory with cd, or provide an absolute or relative path. If the specified file does not exist, gedit may treat it as a new document that can be saved under that name. Creating the file still requires write permission for the target directory.

To learn more about Linux paths, see showing the full path of shell commands and the Linux file structure.

Working with Multiple Documents and Tabs

A tab is a document selector that lets several open files be managed in one editor window. Each open document can appear in its own tab, usually identified by its file name.

• Select a tab to switch to that document.
• Open additional files through the file chooser or by opening them from a terminal.
• Use tabs to compare related files or move between source files without managing several windows.

Changes belong to individual documents. If several tabs contain unsaved edits, save each modified document separately. A modified indicator in a tab or title bar can help identify documents that still need saving.

Core Text-Editing Operations

gedit supports the basic operations needed for everyday text editing:

• Enter text: Click in the document area and type.
• Select text: Drag across characters, words, or lines, or use keyboard selection commands.
• Copy: Place selected text in the clipboard while leaving the original in place.
• Cut: Remove selected text and place it in the clipboard.
• Paste: Insert clipboard contents at the cursor position.
• Delete: Remove selected text or characters near the cursor.
• Undo: Reverse a recent edit.
• Redo: Reapply an edit that was undone.
• Save: Write the current document to its file.

The clipboard provides a convenient way to move or copy text within one document or between gedit and other applications. Use a new document when you want to create a file from scratch, draft temporary text, or paste content before choosing a file name and location.

Finding and Replacing Text

Search and replace locates text in the current document and optionally substitutes it with another string. Searching is useful when a document is too large to scan manually. Replacing is useful for correcting a repeated misspelling, changing an outdated phrase, changing an identifier, or updating a configuration value.

1. Open the find interface and enter the text to locate.
2. Move through matching occurrences and check the surrounding context.
3. Enter replacement text if a substitution is needed.
4. Replace one occurrence at a time when precision matters, or use bulk replacement only after confirming the match is appropriate.
5. Save the document after reviewing the result.

Syntax Highlighting

Syntax highlighting uses colors or other visual styles to distinguish elements of programming languages and structured text. For example, a Python file may display keywords, strings, comments, and other elements in different colors. Representative languages supported by gedit versions include C, C++, Java, and Python.

Highlighting improves readability and makes code easier to scan, but it does not compile, validate, or execute the file. A Python file can look correctly highlighted while still containing syntax errors. Use an appropriate interpreter, compiler, or syntax-checking tool to verify code.

If expected colors do not appear, check the selected language mode and confirm that the file has an appropriate name or extension. Highlighting may be disabled, unavailable for a file type, or unable to identify the language automatically.

Spell Checking and Language Support

gedit can provide multilingual spell checking for prose-oriented documents. Spell checking compares words with a dictionary for the selected writing language and identifies possible spelling errors.

When the feature is available, select the language that matches the document. This improves results for documents written in different languages. Spell checking is less suitable for source code, commands, technical identifiers, and file paths because dictionaries may not contain those terms. Treat warnings about such words as suggestions rather than automatic proof of an error.

Appearance and Readability Settings

Editor preferences can usually be used to configure the font and color scheme. A readable font size, suitable typeface, and strong color contrast can reduce eye strain and make text easier to inspect.

• Choose a proportional font for ordinary prose if that is comfortable.
• Choose a monospaced font when aligning code or configuration values is helpful.
• Use a light or dark color scheme according to lighting conditions and accessibility needs.
• Check that syntax colors remain distinguishable against the selected background.

Preferences may also contain the spell-check language and available plugin controls. Names and locations of settings can vary between installed gedit versions.

Printing and Print Preview

gedit can provide printing as an optional output workflow for text documents. Print preview displays how the document is expected to appear on paper before printing.

1. Open the print command for the current document.
2. Choose print preview if it is offered.
3. Inspect page breaks, margins, text size, and the overall layout.
4. Proceed to print only when the preview is satisfactory.

Print preview is especially useful because a plain-text document may wrap or divide across pages differently from what is visible in the editing area.

Plugins

A plugin is an optional extension that adds capabilities beyond core editing. gedit can be extended through plugins, but the available collection depends on the installed version and Linux distribution.

Inspect the plugin settings to see which additions are installed and available. Enable only plugins that are useful to you, and remember that a feature described for one gedit release may not be included in another. An optional plugin package may also need to be installed through the distribution's software-management tools.

Feature Overview

Practical Workflows

Open and edit an existing file from a terminal

1. Open a terminal in the relevant directory, or identify the file's path.
2. Run gedit FILE_NAME, replacing FILE_NAME with the actual name or path.
3. Edit the document in the gedit window.
4. Save the document and confirm that the correct file is being changed.

Edit several related files

1. Open multiple text or source files.
2. Identify each document by its tab.
3. Switch between tabs while comparing or editing the files.
4. Save every tab that contains changes.

Review a Python source file

1. Open the Python file in gedit.
2. Observe the visual distinction between elements such as keywords, strings, and comments.
3. Use the colors to scan the file, but do not treat them as validation.
4. Run a suitable Python syntax checker or interpreter separately when verification is required.

Correct repeated text in a note

1. Search for the repeated misspelling or outdated phrase.
2. Review each match and choose individual or bulk replacement as appropriate.
3. Inspect the corrected passages for unintended changes.
4. Save the note.

Prepare a document for printing

1. Open print preview.
2. Inspect the expected layout, page breaks, and readability.
3. Print only if the preview meets your expectations.

Troubleshooting

“gedit: command not found”

gedit may not be installed, or its executable may not be available through the current command path. Confirm that gedit is installed with your Linux distribution's software-management tools, then try the command again.

A file cannot be saved

The file or its directory may not be writable, or the target location may be read-only. Save a copy in a writable location, or adjust permissions only when you are authorized to do so. Be particularly careful with system configuration files.

Expected code colors do not appear

The language may not have been recognized, the file type may not be supported, or syntax highlighting may be disabled or unavailable. Check the selected language mode and give the file an appropriate name or extension.

The spell checker flags code or technical vocabulary

The active dictionary may not contain identifiers, commands, or specialized terms. Select the correct language and use spell checking mainly for prose. Evaluate technical-word warnings manually.

A plugin feature is missing

The plugin may be disabled, absent from the installed gedit version, or supplied by an optional package that is not installed. Inspect plugin settings and check package availability through your distribution's software-management tools.

Key Points

• gedit is a graphical general-purpose plain-text editor associated with GNOME.
• Use the application launcher or run gedit FILE_NAME from a terminal to open files.
• Tabs, clipboard operations, undo and redo, search and replace, and saving support everyday editing.
• Syntax highlighting improves code readability but does not validate or run code.
• Spell checking is most useful for prose, while technical terms may be flagged incorrectly.
• Fonts, color schemes, print preview, and optional plugins can adapt gedit to different workflows.