Use reset when a program leaves your Linux terminal unreadable or input behaves oddly. A clean screen and a broken Bash startup file need different fixes.
Choose the command that matches the problem
A terminal emulator keeps screen content, terminal modes, and a scrollback buffer. Your shell configuration and command history live elsewhere, so resetting the terminal does not restore a shell file or erase stored commands.
| Situation | Use | What changes |
|---|---|---|
| You want the prompt at the top of a clean screen | clear or Ctrl+L | Clears the visible display. Your terminal settings stay in place. |
| Text is garbled, input does not echo, or a program left the terminal in a bad state | reset | Reinitializes terminal modes and sends terminal-specific initialization data. |
| Input settings are the issue and you want to keep the screen | stty sane | Restores common terminal line settings without clearing the display. |
| Bash fails when a new interactive shell starts | a backup and a corrected .bashrc | Repairs shell startup configuration, not terminal state. |
Recover a garbled terminal with reset
The reset command reads terminal capability data from TERM and restores the terminal to a usable state. The reset manual page describes it as a terminal-state recovery command after a program leaves the terminal abnormal.
reset
Press Enter even if the characters you type are hard to see. If Enter does not work, try Ctrl+J, which sends a line-feed character.
Reset is part of the ncurses toolset on many Linux distributions. It is interactive, so the repaired state appears in your terminal window rather than as ordinary command output.
When reset needs TERM
TERM tells reset which terminal description to use. A normal terminal emulator sets it for you. If a stripped-down environment has no TERM value, open a regular terminal session rather than guessing a terminal type.
The Linux command-line tutorial explains the environment variables and terminal programs behind this behavior.
If your command runs under a different shell than Bash, identify it before changing startup files. The overview of Linux shell types helps you separate a terminal issue from shell-specific configuration.
Clear the display without resetting terminal modes
Use clear when the terminal works and the display is only crowded. Ctrl+L asks many shells to perform the same display-cleaning action, although the exact scrollback behavior belongs to your terminal emulator.
clear
Clear leaves input modes alone, which makes it the narrower choice for an otherwise healthy session.
Restore input settings with stty sane
A program that exits badly can leave echo disabled or change line handling, and stty sane restores a conventional set of terminal settings while leaving the screen where it is.
stty sane
When reset is necessary, the tput documentation describes its terminfo-backed terminal reset capabilities.
Repair a damaged Bash startup file
A terminal reset cannot fix a syntax error or unwanted command in .bashrc. Bash reads that file when it starts an interactive non-login shell, so first save the current file and inspect it before replacing anything.
cp ~/.bashrc ~/.bashrc.backup
nano ~/.bashrc
Use an editor you already know. If you end up in Vim by accident, follow the steps to exit Vim safely instead of killing the terminal.
If you decide to restore a distribution-provided skeleton, check that your system has /etc/skel/.bashrc first. Copying it replaces your current startup choices, which is why the backup comes first.
test -f /etc/skel/.bashrc && cp /etc/skel/.bashrc ~/.bashrc
source ~/.bashrc
Read how Bash startup files work before moving aliases, PATH changes, or exported variables back into the file. That separation helps you restore only the line that caused the failure.
Keep terminal recovery separate from history and jobs
Reset does not remove commands from your shell history file. History can be useful for recovery and auditing, so do not erase it merely because the screen looks wrong.
If a command still owns the terminal, stop or manage that job before diagnosing the display. The guide to Linux job control explains how foreground and background jobs affect the prompt.
A short recovery order
- Run clear when the terminal is healthy but the display is crowded.
- Run stty sane when input echo or line handling looks wrong.
- Run reset when output is garbled or the terminal state is damaged.
- Open and repair .bashrc only when a new Bash session fails in the same way.
After the prompt returns, run a harmless command such as pwd. If a terminal emulator still renders unusable text after reset, close that emulator window and start a new session.
Frequently asked questions
Use the smallest recovery command that matches the symptom. That keeps a cluttered screen, a damaged terminal state, and a broken shell configuration from becoming the same troubleshooting problem.