Even though you can't see what's happening, Vim is still processing the keys.Īnother way to recover would be to start a new PowerShell terminal, then run: wsl ~ -e bash -noprofile -norc
That's basically trying to get Vim back into a state where it can accept a "quit" command ( : q). Knowing this, you can likely recover from it with something like: So vi is running as soon as you source your ~/.bashrc (or restart your shell). al.) does not go to the screen, but instead is captured to be interpreted ( eval'd) by the shell. This is a subshell that is not interactive, and thus does not have a terminal attached to it. What's happening is that vi is running in a Bash command substitution. If you enter that line, you'll see the same error message, and the terminal will hang again. The last line in your ~/.bashrc is interpreted as: eval "$(vi ~/.config/starship.toml init bash)" You then redefined the starship command as an alias in Bash above that with: alias starship='vi ~/.config/starship.toml' When you install Starship, it tells you to add the following line at the bottom of your ~/.bashrc: eval "$(starship init bash)" While your most recent edit says that you regained control over the terminal, my guess is that the error will reappear the next time you start WSL. This appears to me to be expected behavior.
And as brought up by muru, the alias most definitely caused the issue in the first place, where I overrode the command eval "$(starship init bash)" (at the bottom of the bashrc file) as a result of the new alias called starship. My guess the issue had nothing to do with the alias addition and was something to do with Starship prompt program.Įdit 3: Answer given by NotTheDr01ds perfectly solved the issue. I didn't really do anything to it, just waited. Looks like correct syntax to me, so now I'm even more confused why this issue is happening.Įdit 2: The terminal hanging just stopped after a while and now I'm able to do work on the terminal again. The only part that I edited was adding a new alias called starship, so just this part:Īlias starship='vi ~/.config/starship.toml' Any way to fix this issue other than reinstalling the whole distro?Įdit 1: I'm able to see the bashrc file through Windows File Explorer. bashrc file but I'm unable to even view that file, let alone edit and execute it. It's almost certain I made some sort of mistake while editing the. I am unable to ctrl+C or ctrl+z my out of anything and no prompts show up to allow for any command typing. bashrc file on VIM where all I did was add in an alias for some ls command.
My terminal for any new Ubuntu instance is completely frozen with the message "Vim: Warning: Output is not to a terminal" Distro: Ubuntu-18.04 (running on Windows 10 WSL2)
0 kommentar(er)
