-
-
Notifications
You must be signed in to change notification settings - Fork 674
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
Git Bash: Terminal starts with error after changing theme #211
Comments
Same here from me, this is happening to me in git-bash on windows. |
Similar here: I get the following whenever I bash: /home/solrevdev/.oh-my-bash/lib/base.sh: line 209: syntax error near unexpected token `('
bash: /home/solrevdev/.oh-my-bash/lib/base.sh: line 209: ` myip () {' Where line 207-212 of bash.sh is # myip: displays your ip address, as seen by the Internet
# -------------------------------------------------------------------
myip () {
res=$(curl -s checkip.dyndns.org | grep -Eo '[0-9\.]+')
echo -e "Your public IP is: ${echo_bold_green} $res ${echo_normal}"
}
System info:
|
@solrevdev The message is the same, but I think the actual problem is different from the original one. In your case, I think the shell function |
That’s it! Thanks @akinomyoga ! That was exactly the issue there was another function named that which I could comment out and bingo! |
I have checked the original issue of PS1='$(echo hello)\n' This seems to be the same problem as discussed here. According to this page, Git Bash 2.6.3 and 2.8.2 seems to have had the same problem. The problem doesn't seem to reproduce in the upstream Cygwin and also in Linux. I have updated Git Bash to 2.37.2 and found that the problem is fixed there. So the solution is just to update Git for Windows: SolutionThe problem is fixed in the latest version of Git for Windows (Git Bash). Please update your Git for Windows: $ git update-git-for-windows |
I changed the theme to
cupcake
and restarted the terminal.It always starts with an error:
The previous theme was
purity
and I didn't have such problems wit it. It is just when I changed the theme that this problem started.The text was updated successfully, but these errors were encountered: