Each time I open my terminal(mac laptop). I get this weird looking error which never goes away. Almost a year now. Please what does it mean?
-bash: command substitution: line 1: syntax error near unexpected token `newline'
-bash: command substitution: line 1: `/usr/libexec/java_home -v <version>'
https://i.stack.imgur.com/4sXcY.png
Although the terminal still works but I don't know what these two lines mean.
Related
My "man" utility on MacOS Ventura 13.1 seems to be broken. When I try running "man ls" from the command line I get:
/usr/bin/man: eval: line 413: unexpected EOF while looking for matching `''
/usr/bin/man: eval: line 414: syntax error: unexpected end of file
I expected to see the man page for "ls" displayed in the terminal. Any ideas how to fix this (short of editing /usr/bin/man itself)?
Oops...please ignore. I found the issue. I had an old setup for MANPAGER that integrates with the "bat" utility for displaying man pages that was the culprit.
When I open my terminal on MacBook Pro I get the below message, but command line seems work fine after this, but I would like to correct this message coming up. MESSAGE:
-bash: occur: command not found
-bash: ----Beginning: command not found
-bash: is: command not found
-bash: other: command not found
Hi today for unknown reason, if I typed the following command "vim \tab" in bash terminal to hopefully get an auto-completion, I get the following error:
$ vim bash: command substitution: line 22: syntax error near unexpected token `}'
bash: command substitution: line 22: ` }'
This error does not happen if I typed '\tab` at the end of other commands such as 'ls', or even an alias of vim such as 'alias v=vim'.
This error does not happen in another gnome-terminal, either.
Not sure what is causing this (a vim plugin?). Any idea? thanks.
Found the root cause. I created an alias done, and the "done" conflicts with the bash keyword "done". Problem solved by renamed the alias.
The error in the title is what appears on my Bash on Windows 10 when I try using make I did read many tips and none seems to work when I tried mingw-get install msys-make.
I got the error message that it's already installed on my pc. Now I dunno what to do, even when the package is installed, bash: make: command not found is still there. On the other hand, I did add almost all the possible path to PATH, and sometimes the error change to
/mingw64/make-4.3/tests/scripts/variables/make: line 3: =: command not found
/mingw64/make-4.3/tests/scripts/variables/make: line 5: =: command not found
/mingw64/make-4.3/tests/scripts/variables/make: line 7: syntax error near unexpected token `q!'
/mingw64/make-4.3/tests/scripts/variables/make: line 7: `run_make_test(q!'
You should add its path to the $PATH variable and reboot Windows. OS updates viriables after reboot.
I've used virtualenv to program using my mac terminal for about 1/2 a year w/no issues. Suddenly today I began to get relative path errors when I tried to load python. There was no apparent reason for it, and eventually I tried restarting my computer.
Then I opened a new terminal window, and these new errors were present for the first time:
-bash: eval: line 4: unexpected EOF while looking for matching `"'
-bash: eval: line 5: syntax error: unexpected end of file
I assume the two misbehaviors are related in some way. Any idea what would be causing it? What files could the terminal be looking at that would cause this? AFIAK, I haven't changed anything on which it would depend.
Thx for any advice!
My guess is that a bash startup file (~/.bashrc, or possibly /etc/profile, ~/.bash_profile, ~/.bash_login or ~/.profile) contains a syntax error, and that causes all sorts of errors for other programs because the setup of the environment they expect does not take place.
From the error message it seems like an unterminated string constant, i.e. a missing ".
The bash manual on startup files has information about this.
You can also try to start bash in debug mode (bash -x (interactive shell) or bash -lx ( login shell)) to try to identify the error.