Integrated terminal does not open after closing
See original GitHub issueI am running code-server using the official docker image and having an issue with the integrated terminal. Initially, using Ctrl+` will open the integrated terminal, and the same keystroke will also hide it. But then using the keystroke again does nothing. There are no log messages even with --log trace
. I’ve also tried using the command palette to run “Toggle Integrated Terminal” which also does nothing.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:14 (6 by maintainers)
Top Results From Across the Web
Integrated terminal does not open after closing #1615 - GitHub
I am running code-server using the official docker image and having an issue with the integrated terminal. Initially, using Ctrl+` will open ......
Read more >Troubleshoot Terminal launch failures - Visual Studio Code
Some terminal launch failures may be due to your shell installation and are not specific to VS Code. The exit codes displayed come...
Read more >VSCode will not open files in new tabs from integrated terminal
Basically, the 'inheritEnv' box needs to be checked. After closing and reopening a terminal, 'code' note works as expected.
Read more >Terminal | WebStorm Documentation - JetBrains
Open : View | Tool Windows | Terminal or Alt+F12 ... The Terminal saves tabs and sessions when you close the project or...
Read more >Vscode Integrated Terminal closes immediately upon opening
Upgrade vscode · Point $SHELL to correct shell path. Find which shell you have, echo $SHELL mine is /bin/zsh after that I checked...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I also meet this problem with safari on iPad in PWA mode.
The same symptom as you.
I just tried vscode.dev on the iPad and
After that I tried with my installation via browser and can’t be reproduced there so it looks like it is a generic issue but just can be reproduced when using the app as a Progressive Web App