New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Falls back to standard prompt after failed command #236
Comments
I was wrong about when it happens, it happens even after a successful command. |
I did some debugging, I don't know whether this is a problem on my system... |
I will however take that into consideration and adjust the code to not fail on that. |
I have the exact same result, how can I go about debugging the profile script? |
I will create a small fix for this based on @firlus fix. |
@mendoncaftw @firlus I did a quick commit which could fix it, would be great if you can confirm this fixes the issue. Still wonderding why it doesn't have a history with timings, but that's something else. |
@JanDeDobbeleer I looked at your PR and changed the script on the profile but I continued to have the default PS> prompt. |
Correct, Scoop only installs the binaries. Although the setup instructions do explain what to alter when installing with Scoop, if you're not proficient in Powershell and only want to go for a Powershell integration, the module is preferred. |
Wow, that was quick, thanks for the help! Thanks for your great tool, I will try to look into creating an own segment since I am trying to learn Go right now and I really love this project! |
Well, you also helped me because following all the instructions about Powershell without mixing in scoop also worked for me. |
Prerequisites
CONTRIBUTING
guideDescription
When I type in a command that e.g. does not exists, the prompt shows only
PS>
after that until I open a new console window.Environment
Steps to Reproduce
This is my $PROFILE:
Expected behavior: See nice prompt again (Even with some form of error sign?)
Actual behavior: Falls back to
PS>
-promptIt seems like it fails to run something in the $PROFILE after a failed command, but this is just a guess...
The text was updated successfully, but these errors were encountered: