I used to debug javascript in VS Code's Terminal.
Recently, I see (eval):1: parse error near "typeset" in my VS Code's Terminal and I cannot debug .js anymore. I googled for a solution but didn't see any.
Don't know for sure if this causes the problem: I wanted to open VS Code from Mac's Terminal, so that in VS Code, I Used Shell to install code in PATH. After that, I see (eval):1: parse error near "typeset" in both Mac's Terminal and VS Code's Terminal.
Please give a hand. Thanks
UPDATE: I have tried to uninstall the code command from PATH in VS Code, but this error message still show in Terminal.
Related
When i hover on my vscode terminal name: (in terminal's upper right corner named "Powershell")
it shows : shell intergartion failed to activate,
how to solve this error, while
I tried installing vs code again but still no change, and also installed powershell 7
There are a few potential solutions for this issue.
Make sure that you have the latest version of VS Code and the Shell Integrate extension installed.
Check that the integrated terminal in VS Code is set to the shell you want to use (e.g. PowerShell, Command Prompt, Bash).
Try running VS Code as an administrator.
If you are using Windows, try adding the path of the shell you want to use (e.g. C:\Windows\System32\bash.exe) to the "terminal.integrated.shell.windows" setting in your VS Code settings.
You can also try reinstalling vscode and the extension.
If none of the above solutions work, you can try searching for specific error messages in the output panel of vscode or in the output of the terminal.
When trying to run a file or just open the terminal in VS Code, the terminal opens for a half second and then promptly closes without error messages.
I've tried updating VS Code, and external libraries/environments. I'm thinking I might need to fully uninstall and reinstall, but hoping there is a easier fix.
Sometimes I open a php file in VS Code and no linting occurs until I open the linting console from the bottom, switch over to the terminal pane where a dialog shows up that asks me if I trust the authors of this workspace. If I say yes then linting errors are shown until I close VS Code.
Other times, I open a php file in vs code, no linting errors show so I open the linting console from the bottom and switch over to the terminal pane but nothing happens.
There is no pattern that I can see as to when the linter will work and when it will do nothing. I have never encountered a problem like this. Does anyone know anything about this problem?
I have this problem with my terminal: when I open it, it shows me a blank terminal and I can't even see the cursor. The windows is opening correctly and there is no error, but I can' type anything in the terminal.
Vs code version is 1.42.0
Also, I tried the compatibilty with Windows is set off
Here you can see what I'm talking about:
screenshot of terminal
I have downloaded VS code, but the debugger doesnt work.
It says no configurations. I put a short video to show you what happens.
Thanks a lot.
short video
I don't think it has anything to do with VS Code. The error is "Cannot find runtime 'node' on PATH", so that leads me to believe you either need to download Node.js and/or add 'node' to your PATH. Run the following line from Command Prompt:
SET PATH=%PATH%;C:\Program Files\Nodejs;
It also wouldn't hurt to reboot afterward.