-
Notifications
You must be signed in to change notification settings - Fork 110
Description
Description
When running curl commands in the terminal to interact with my Axum server API, after the command finishes, the shell prompt (e.g., user@pop-os) does not appear at the start of a new line. Instead, the prompt is appended directly to the end of the command output, causing the prompt to overlap or overwrite part of the output. As a result, the prompt disappears from its normal position, and trying to type a new command results in corrupted or invalid input. This behavior effectively breaks the command line until the terminal is reset.
How to reproduce
- Start the Axum server locally (e.g., on 127.0.0.1:3000).
- Open a terminal and run a curl command.
- Observe that the shell prompt does not appear on a new line after the output, but directly after the last character.
- Attempting to type a new command results in corrupted input or makes the command invalid.
Expected Behavior
The shell prompt should be displayed properly on a new line, ready to accept user input without overlapping the command output or losing characters.
Actual Behavior
The shell prompt is appended directly to the end of the command output without a newline, causing overlapping characters, visual glitches, and invalid command input until the terminal is reset or corrected manually.