Create and Edit Text Files in Linux

Servers and certification labs rarely give you a graphical editor. You create notes, scripts, and configuration snippets from the shell, so knowing when to use touch, redirection, Vim, or Nano saves time and prevents accidental data loss.

Ways to Create and Edit Text Files in Linux

Linux stores plain text as a byte stream. You can create or change files entirely from the terminal.

Pick the smallest tool that fits the job. One-line updates belong in redirection; reviewing ten lines of /etc belongs in Vim or Nano. Deeper pipe and stderr ordering lives in the redirection and pipes lesson; copy and delete workflows sit in Linux file management.

Linux Text Editing Quick Reference

Create an Empty Text File

An empty file has zero bytes. Use one when a program expects a path to exist, as a placeholder before you edit, or to refresh a timestamp.

touch creates the file if missing and updates timestamps if it already exists:

touch empty-by-touch.txt

ls -l empty-by-touch.txt

-rw-r--r--. 1 root root 0 Aug  7 22:59 empty-by-touch.txt

Shell redirection with no command output also creates or truncates a path:

: > empty-by-redir.txt

stat -c '%n %s bytes' empty-by-redir.txt

empty-by-redir.txt 0 bytes

When the path already holds data:

• touch existing.txt updates timestamps but does not remove content.
• > existing.txt or : > existing.txt truncates the file to zero bytes before any new data is written.

Treat a single > as destructive on existing files. Copy the original first when you need a backup.

Write Text Without an Interactive Editor

Run the examples in a directory you own, such as ~/edit-lab or /tmp/edit-lab.

One line with echo

echo 'first line' > oneline.txt

cat oneline.txt

first line

Formatted lines with printf

printf 'line one\nline two\n' > printf-demo.txt

cat printf-demo.txt

line one
line two

Append with >>

echo 'appended' >> oneline.txt

cat oneline.txt

first line
appended

Redirect piped input with cat

printf 'typed line one\ntyped line two\n' | cat > typed.txt

cat typed.txt

typed line one
typed line two

Here document

cat > heredoc-demo.txt << 'EOF'
server_name example.local
port 8080
enabled yes
EOF

cat heredoc-demo.txt

server_name example.local
port 8080
enabled yes

Quoting the delimiter ('EOF') prevents variable expansion inside the block. For stdout, stderr, and pipe ordering beyond > and >>, see redirection and pipes.

Truncation warning

A single > replaces existing content:

echo 'original content' > overwrite-demo.txt
echo 'new only' > overwrite-demo.txt

cat overwrite-demo.txt

new only

The second redirection removed original content entirely.

Understand Vim Modes

Vim behavior depends on the active mode. Certification labs and rescue images expect you to move between them without thinking.

The status line shows -- INSERT -- while you are in insert mode. Always press Esc before :wq or other command-line actions.

On RHEL and Fedora, vim-enhanced provides /usr/bin/vim. Minimal images may ship only vi from vim-minimal—install the full package with sudo dnf install vim-enhanced when the vim binary is missing.

Open, Edit, Save, and Exit with Vim

Open an existing file or create a new path:

vim sample.txt

If the path is new, Vim shows a [New File] hint at the bottom:

From normal mode, press i to insert before the cursor. The status line shows insert mode:

Type your text, press Esc, then save and quit with :wq:

Other exits you will use often:

• :w — write without quitting
• :q — quit when the buffer is unchanged
• :q! — quit without saving

If you type :q after edits, Vim reports E37: No write since last change. Use :wq to save or :q! to discard.

Practice open → i → type → Esc → :wq on a scratch file until the sequence is automatic.

Navigate Inside Vim

Movement happens in normal mode. Arrow keys work; these keys keep your hands on the main keyboard:

Show line numbers when you compare a file to documentation:

:set number

Turn them off with :set nonumber. For relative and hybrid numbering, see Vim line numbers.

Search and Replace Text in Vim

Search forward from normal mode with /pattern or backward with ?pattern. Press n for the next match and N for the previous match.

Replace on the current line:

:s/old/new/g

Replace on every line:

:%s/old/new/g

Add c to confirm each replacement:

:%s/old/new/gc

Example workflow on a scratch file—create it, edit in Vim, then verify:

printf 'find old\nfind old again\n' > srdemo.txt

Inside Vim: :%s/old/new/g, then :wq.

cat srdemo.txt

find new
find new again

Copy, Delete, Paste, Undo, and Redo in Vim

Run these in normal mode:

Delete the first line of a demo file:

printf 'delete this line\nkeep this\npaste below\n' > modify-demo.txt

In Vim: gg, dd, :wq.

cat modify-demo.txt

keep this
paste below

To copy a line: position the cursor, yy, move with j or k, then p.

Edit Files with Nano

Nano is a simpler full-screen editor. Shortcuts are listed at the bottom; ^ means Ctrl.

nano notes.txt

Nano fits quick edits when you do not want to memorize Vim modes. Servers and exam environments still expect terminal editing—this guide stays on the command line.

Edit System Configuration Files

Paths under /etc usually belong to root. Read when permissions allow; save with elevation. The example below touches OpenSSH server settings—confirm you still have SSH access before you change listener or authentication options.

Back up before you edit:

BACKUP="/etc/ssh/sshd_config.bak-$(date +%F-%H%M%S)"
sudo cp -a /etc/ssh/sshd_config "$BACKUP"

-a preserves permissions and timestamps on the copy.

Open the file with elevation:

sudo vim /etc/ssh/sshd_config

Replace vim with nano if you prefer. Elevation applies to the editor process so you can write the protected path.

Validate before you reload — editing the file does not apply changes until the service reloads. Many daemons ship a syntax check:

sudo sshd -t

When the file is valid, sshd -t exits silently with status 0. Fix reported line numbers before you reload with systemctl (for example systemctl reload sshd). Shell scripts use bash -n script.sh for the same kind of syntax-only check.

Compare Two Versions After Editing

After you change a file, compare it to the backup you kept:

sudo diff -u "$BACKUP" /etc/ssh/sshd_config

The -u unified format shows removed lines with - and added lines with +.

To check one setting without scrolling the whole file, use grep:

grep -n '^#*Port' /etc/ssh/sshd_config

Keep cp file file.bak or a timestamped copy in your routine before you touch production configuration.

Common Vim Problems

Permission denied from the shell

Run this example as a normal, non-root user. Root can bypass ordinary write-permission checks on many systems, so the failure below is not reproducible from a root shell.

A file without the write bit rejects redirection even in /tmp:

printf 'secret\n' > /tmp/protected.txt
chmod 444 /tmp/protected.txt
echo 'fail' >> /tmp/protected.txt

bash: /tmp/protected.txt: Permission denied

Use sudo with your editor or restore write permission when appropriate.

Common Nano Problems

Practical Editing Example

This walkthrough edits a small application-style config in a lab directory—not a production system file.

Create the starting file:

mkdir -p /tmp/edit-lab && cd /tmp/edit-lab
cat > app.conf << 'EOF'
# Sample app settings
debug no
timeout 30
log_level info
EOF

cp -a app.conf app.conf.bak

Open app.conf in Vim (vim app.conf). In normal mode:

1. Search for the timeout line: /timeout then Enter.
2. Move to the value word: w (next word after timeout).
3. Change that word: cw, type 60, then Esc.
4. Move to the last line with G, press o to open a new line below, type retry 3, then Esc.
5. Save and quit with :wq.

After /timeout, the cursor sits on the word timeout—w advances to 30, and cw replaces that word and enters insert mode for the new value.

Verify the change without re-opening the editor:

grep -E 'timeout|retry' app.conf

timeout 60
retry 3

Compare against the backup:

diff -u app.conf.bak app.conf

--- app.conf.bak	2026-08-07 22:59:16.925079644 +0530
+++ app.conf	2026-08-07 22:59:26.638617614 +0530
@@ -1,4 +1,5 @@
 # Sample app settings
 debug no
-timeout 30
+timeout 60
 log_level info
+retry 3

The diff shows exactly what changed before you would deploy the same rhythm on /etc paths with sudo, sshd -t, and a service reload.

References

• Vim documentation
• GNU nano manual
• GNU Coreutils touch
• Bash redirection

Summary

You can create and change text files entirely from the shell. Empty placeholders come from touch or : > file, quick updates from echo, printf, and >>, and scripted blocks from here documents—each with a different risk when the target path already exists.

Vim is the editor to learn for servers and labs: normal, insert, and command-line modes plus a small set of motion and editing commands cover most configuration work. Nano remains a friendly alternative when the shortcut bar at the bottom is enough.

Protected files need a slower rhythm: sudo your editor, keep a timestamped backup, run a validator such as sshd -t or bash -n when one exists, and read diff -u before you reload a service. Treat a lone > as truncate, watch for Vim swap files, and rehearse the open → insert → save sequence on scratch files before you edit live configuration.

Next, practice copy and delete workflows in Linux file management, or return to Linux command line basics for quoting and tab completion.