You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Going back in the commands history with the up arrow key, and then going back to the latest commands will keep characters from previous commands in front of the prompt.
Steps to reproduce:
enter a command (for example ls -la | grep foo
go back in the commands history with the up arrow
go all the way forward to the prompt with the down arrow
characters will be "stuck" in the prompt
Expected Behavior
The prompt should remain unchanged/clean when going back and forward in the command history.
This is interesting, I have had the same issue but never before connected it to Starship. I thought it was an issue with how I have readline setup, especially as I get the same behaviour when Starship doesn't display (exact same behaviour when in an interactive Python session launched by my bash).
I don't really have any further insight into this, but I did implement a workaround, which is this line in my .inputrc
"\C-f": redraw-current-line
which is equivalent to running this bash command, if you don't use .inputrc,
bind'"\C-f": redraw-current-line'
which just means that pressing ctrl-f will redraw the input line, and the phantom characters go away.
Bug Report
Current Behavior
Going back in the commands history with the up arrow key, and then going back to the latest commands will keep characters from previous commands in front of the prompt.
Steps to reproduce:
ls -la | grep foo
Expected Behavior
The prompt should remain unchanged/clean when going back and forward in the command history.
Additional context/Screenshots
https://i.imgur.com/F9zFjKi.gif
Possible Solution
None that I have found
Environment
Relevant Shell Configuration
Starship Configuration
The text was updated successfully, but these errors were encountered: