Why does a command-line prompt sometimes appear to wait for more input?

It may be waiting for another line to finish a command you started. In an interactive Bash session, Bash displays a secondary prompt before reading subsequent lines of a multiline command. That prompt’s text is configurable, so its appearance alone does not explain what Bash is waiting for. [S1]

First, pause and read the command from its beginning. Don’t treat the changed prompt as proof that the command is safe or that one particular character is missing. If you are unsure what the pending input would do, avoid pressing Enter just to see what happens. Check which shell you are using and consult its documentation before deciding how to abandon the input.

In Bash, check for syntax that visibly starts but does not finish. One concrete example is a single quote without a matching single quote: Bash preserves characters inside single quotes until it finds the closing quote. A backslash immediately followed by a newline outside quotes is another case: Bash treats that pair as a line continuation and removes it from the input. [S2]

For example, suppose you intended to print a short phrase and typed printf '%s' 'hello before pressing Enter. The final single quote is missing, so the input is not complete. If you are confident the original command is harmless and that this is the only issue, you could type the matching quote on the next line. Note that the newline you already entered becomes part of the quoted text. Inspect the whole command first: this example illustrates one Bash quoting rule; it does not establish that every continuation prompt has the same cause.

No. In Bash, the secondary prompt indicates that Bash is reading more command input, but its text is configurable and does not, by itself, identify why the input continues. [S1] Compare the command you entered with the syntax you intended, including its quotes and any visible backslashes. If that comparison does not make the issue clear, don’t add punctuation at random: a guessed character may change what the command means. The cited Bash rules should not be assumed to describe every other shell; identify your shell before relying on them.

If you want to abandon the input, use the interruption or cancellation method documented for your shell and terminal. The Bash references here explain secondary prompts and quoting, not the exact cancellation behavior of every shell, terminal, or command, so this guide cannot promise that one keystroke will have the same effect everywhere. If the terminal’s context is unclear, consult its documentation or ask someone familiar with that environment. Before continuing, make sure you know whether you have an unfinished command or a different program awaiting input.

Quick check:

1. Note which shell you are using, if you know.
2. Read the full command already entered; don’t press Enter merely to test it.
3. In Bash, inspect for an unmatched single quote or a backslash followed by a newline outside quotes.
4. Remember that the secondary prompt alone does not reveal the cause.
5. If you don’t understand the pending input, use the shell’s documented cancellation method rather than adding characters by guesswork.