I started my gitpod vscode environment as usual today but for some weird reason the terminal is not working meaning its not showing anything. if I start a new terminal than also its showing nothing instead of its name like bash.cursor not blinking, I am not able to type anything.
Related
I am trying out the Remote - Containers VSCode extension. I get a docker warning and a prompt message if I want to continue but I can't type anything into the terminal. The cursor looks like it's active but nothing happens when I type.
So far I have tried:
Using iTerm.app instead of Terminal.app (in VSCode settings)
Disabled oh-my-zsh terminal plugin
Quit and start Visual Studio code
I solved this by using generating ssh key in the devcontainer and adding it to github.
My macOS terminal is showing Process completed when I type any thing. I am not able to type or do anything on terminal (This effect my Android Studio and VsCode terminal also they just open close in an second) So all issue are causing with this terminal I try every thing restore profile etc nothing is working for me.
But one thing is strange here when I restart my Mac terminal works fine but after I work on android studio or vscode with Mac terminal (Not there default terminal because they are not working) After 1 hour same happen as I say before and as in screenshot.
On different questions solutions was to type /bin/bash -x on terminal but I can't even type single character on this.
I am finding solution for this from 1 week and not able to find any thing I need to restart me laptop every 1 hour to work.
I am using BigSur with M1 processor.
Also it was working fine before but I work on Flutter so I have set path and run commands like
Run: nano ~/.zshrc
Add: export PATH=[PATH_TO_FLUTTER_GIT_DIRECTORY]/flutter/bin:$PATH
Run: source ~/.zshrc
And some bash commands to set path.
I'm a beginner and I'm getting a bash syntax error Unexpected token '&'
Initially, I was getting this error while using a virtual environment in python.
But today I cleaned my PC and reinstalled the window and now I can't even run normal programs.
Cause of Error -> I'm using VS Code and terminal as Git Bash.
After wasting days I got to know that this is happening because Bash and PowerShell have different syntax
and when I'm running the code the vs code is not adapting to bash's syntax (and yes it works on PowerShell).
And Default terminal is also set to Git Bash in my JSON setting file like this:
"terminal.integrated.defaultProfile.windows": "Git Bash",
I tried changing to another famous way:
"terminal.integrated.shell.windows":"path_here"
and it does not work either and says deprecated method.
How can I change the default Syntax of vs code terminal?
Do I have to reinstall the bash and change something in my options?
And I was using bash b4 as well but never faced this issue but then I recently started using virtual env
then this error occurred for the first time.
So I'm confused whether this is an in-built problem or something that I can fix?
And I found many ppl with the same type of question (which are posted recently that leads me to think it could be a fault from their side) in StackOverflow but no one was able to define it hence I'm adding this one.
Yes, i was right. The issue was in the VScode itself. Today there was an update and everything seems to be normal/working now.
But today I cleaned my pc and reinstalled the window and now i can't even run normal programs.
Make sure your %PATH% environment variable does include C:\Program Files\Git\bin\ in order to know about bash.exe
Try and launch, for testing, VSCode after setting the PATH in a CMD with:
set GH=C:\path\to\git
set PATH=%GH%\bin;%GH%\usr\bin;%GH%\mingw64\bin;%GH%\mingw64\libexec\git-core;%PATH%
rem Then, in the same CMD
"%LOCALAPPDATA%\Programs\Microsoft VS Code\bin\code.cmd"
I have a Go project that I'm maintaining with vscode.
I have set the GOPATH for the project using the go.gopath setting in vscode, and this seems to work just fine for the most part.
However, when I open the integrated terminal, and type echo $GOPATH, the value shown is the value from .bashrc not the value from go.gopath.
I need the integrated terminal to respect the GOPATH that's defined by vscode so when I run commands in the terminal, everything runs properly.
I've tried setting values in terminal.integrated.shell.osx and terminal.integrated.shell.osx, but nothing seems to do what I want.
I want the intergrated terminal to understand the proper GOPATH when vscode is opened, and not have to manually set this each time I open an instance of the terminal.
I've found resources that seem like the should work, such as https://github.com/Microsoft/vscode/issues/14973 and many others, but nothing seems straight forward.
VSCode uses go.gopath i used for tools like go vet and go import... You will have to export the GOPATH on the integrate terminal with each use or set it in the bashrc... the integrate terminal is just a "clone" of the systems actual terminal. If you read the thread you provided you'll notice that what you want is a feature requests and not a current feature
-bash: sencha: command not found
I just spent a few hours trying to make this Sencha Cmd works on my MacBook, but just couldn't. I uninstalled a previous version and just couldn't get it to work again. I always get the
-bash: sencha: command not found
error. I did try everything in this post, without success.... I even get an error when I call
.bash_profile
stating that it's not found... Do you have any idea what could be the problem ?
I'm fairly new to the Linux command world so I might miss a point here. Maybe I might use "sudo" to be granted acces to bask_profile ?
EDIT : I got it working for the current bash session. I position myself at the user root (~/) and call ". .bash_profile"(the space is important here). BUT... it only works for the current session. As soon as I close Terminal and reopen it, I loose everything :-(
OK, just so you know, I managed to fix the damn thing be opening and editing the ".bash_profile" file in a text editor (TextMate for me). This is an hidden file, but you can configure your Mac to show those files in Finder. The file is located at your user's root. It is quite annoying to have to spend hour messing in path and environment variables in 2013... Installer should do those things and reports error if something happens in the install process.