求助：终端无法输入字母'i'，输入'e'时重复输出's'

Hey there, let's dig into this frustrating terminal keyboard glitch you're dealing with—super weird that your 'i' key vanishes only in the terminal, and 'e' spams 's' out of nowhere, right? Since this started after visiting a sketchy link, odds are something messed with your shell/terminal configuration. Let's fix this step by step:

1. Reset Terminal Input Settings Immediately #

First, try resetting your terminal to sane defaults—this often fixes wonky key behavior with a single command:

stty sane

Or if that doesn't work, run:

reset

These commands wipe out any temporary terminal input overrides that might have been injected.

2. Check for Accidental Shell Editing Mode Triggers #

Bash/zsh have vi and emacs editing modes that can rewire key functions. Let's confirm which mode you're in:

set -o

Look for vi or emacs marked as on. If it's vi mode, switch back to the default emacs mode with:

set -o emacs

If that fixes the issue, you might have accidentally hit Ctrl+V or another shortcut to toggle modes.

3. Audit Your Shell Configuration Files #

Malicious scripts often sneak changes into your shell's config files. Check these files for suspicious key bindings:

• ~/.bashrc (for bash users)
• ~/.zshrc (for zsh users)
• ~/.inputrc (global input settings)

Search for lines that modify 'i' or 'e' behavior:

grep -n "bind\|readline" ~/.bashrc ~/.zshrc ~/.inputrc | grep -i "i\|e"

If you see anything like bind 'i:delete-char' or bind 'e:"sssss"', delete those lines and restart your terminal.

4. Test with a Clean User Session #

Create a temporary test user (or log into another existing user) and open their terminal. If the keys work normally, the problem is definitely in your main user's config files. You can either:

• Restore your config files from backups (if you have them)
• Delete the suspicious lines found in step 3
• Reset your config files to default (e.g., rename ~/.bashrc to ~/.bashrc.bak and let the shell generate a new one)

5. Check for Suspicious Background Processes #

Run this command to list active processes and look for anything out of the ordinary (like unknown scripts running in the background):

ps aux | grep -v grep | grep -i "terminal\|input\|keylog"

If you spot a suspicious process, kill it with kill <PID> (replace <PID> with the process ID number).

6. Try a Different Terminal Emulator #

If none of the above works, install or switch to a different terminal app (e.g., from GNOME Terminal to Konsole on Linux, or iTerm2 to Mac's default Terminal). If the keys work in the new terminal, your original emulator's configuration was corrupted—reset its settings to default in its preferences menu.

If all else fails, a quick system reboot can sometimes clear out lingering malicious processes or stuck settings.

内容的提问来源于stack exchange，提问作者Khan Saad Bin Hasan