-
Notifications
You must be signed in to change notification settings - Fork 49
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
Entering git repo throws "Cannot find gitstatus.sh" #38
Comments
can you please run |
Here's the difference between path variables in zsh and bash:
The file was present in the
|
Hey, I found the same issue running that on WSL here is my $PATH after running bootstrap.sh
|
I personally didn't look into it yet, though I have a feeling that it has to do with |
I have the same issue on WSL. Have you found any solutions @GersonDias ? |
On wsl, I managed to prevent throwing "Cannot find gitstatus.sh" by executing |
I fixed this issue by copying function git_prompt_dir() {
# assume the gitstatus.sh is in the same directory as this script
# code thanks to http://stackoverflow.com/questions/59895
if [ -z "$__GIT_PROMPT_DIR_BASH" ]; then
local SOURCE="${BASH_SOURCE[0]}"
while [ -h "$SOURCE" ]; do
local DIR="$( cd -P "$( dirname "$SOURCE" )" && pwd )"
SOURCE="$(readlink "$SOURCE")"
[[ $SOURCE != /* ]] && SOURCE="$DIR/$SOURCE"
done
__GIT_PROMPT_DIR_BASH="$( cd -P "$( dirname "$SOURCE" )" && pwd )"
fi
} The comment says it all. The code assumes that gitstatus.sh is in the same directory with gitprompt.sh |
Not sure what this is. Had this error once before, couldn't find the culprit and had to do clean install. Now after a few days of using the dotfiles again seeing this error.
Re-running
bootstrap.sh
did not help. The file is clearly present in the/bin
folder, however still getting this error.Oh, and thanks for these awesome dotfiles!
Upd: I've noticed my shell got switched back to bash instead of zsh. Switching to zsh made the issue disappear. But should this work under bash shell as well?
The text was updated successfully, but these errors were encountered: