I have setted up vscode to run zsh as default. Yesterday I ran an update in vscode yesterday and since then I've lost the history.
It seems that it opens its own instance.
echo $HISTFILE
/var/folders/79/yxms393s2510hr4cnmzj5z1m0000gn/T/nikos-code-zsh/.zsh_history
Any ideas on how I could revert that change?
This was reported to the vscode repository and a fix was created already. It's available in the insiders release and to the standard release today.
#168396
already fixed in insider's and soon to be fixed in our recovery release (tomorrow)
Related
Whenever I update my VSCode, few of my extensions gets inactive automatically. It's get activated if I uninstall the extension and reinstall it. you can find in the screen shot that few are inactive.
Very likely those extensions are outdated and are known to have compatibility problems with the current vscode version. Try updating those extension to their latest version.
Also check if you use the latest vscode version.
I can't open a new external terminal with CTRL + SHIFT+C. Did a new update remove this function? I was able to use this shortcut before, but now I cannot.
This appears to be a bug with the current version of Visual Studio Code, as multiple users are reporting it isn't working across different operating systems:
GitHub Issue #1
GitHub Issue #2
I updated to 1.57 the other day, and it is not working for me now either. Previously it was on a slightly older version that I updated from.
Update:
The latest Visual Studio Code Insiders release (1.58) has addressed this as noted in this GitHub issue. If you really want this functionality back, you can download the Insiders edition, otherwise you'll need to wait until the next update for the main application.
Final Update:
The May Recovery update resolved this issue. Download the update, and you should be able to once again open external terminals through the command.
It was the issue vscode 1.57 which lasted for about an week.
If you upgrade to the latest version of vscode, it will work now.
Good Job VSCODE !
I have set my integrated default terminal in VSCode as Git Bash but whenever I launch VSCode, powershell pops up instead of bash. It does not, however, change the default terminal setting but it is irritating.
I have tried removing the profile of powershell from settings but that seems to do nothing.
Why is this happening?
Make sure you upgrade to vscode v1.60.1 - there is a fix in that point release for this issue.
See Select Default Profile do not actually open gitbash. After relaunch, on startup, it just keeps open PowerShell.
The same thing was happening to me and the referred to fix in the Insiders' Build 05/14/2021 did in fact fix it for me. In the meantime, opening another terminal does always open git bash for me - but that is a pain.
This worked for me:
{
"terminal.integrated.defaultProfile.windows": "Git Bash",
"terminal.integrated.profiles.windows": {
"PowerShell": null,
"Git Bash": {
"source": "Git Bash"
},
"Windows PowerShell": null
},
"terminal.integrated.automationShell.windows": "Git Bash",
"powershell.enableProfileLoading": false,
"powershell.integratedConsole.showOnStartup": false
}
I managed to find a workaround without using the Insider's Build that may work for some of you : I removed all profiles safe for the one I want, and reinstalled VS Code. Then it somehow started using the right terminal on startup. I don't know if this works without disabling all other profiles though.
I was still having this issue, and what worked for me was:
When PowerShell opened, I reset GitBash to my default, and then killed the terminal (so there were no terminal's running).
Removed the terminal panel from view by clicking the X in the top right
Closed VSCode
When I opened my codebase again and showed the terminal, it began working.
Just did an update to version 1.60.1
and it fixed it.
From the release notes the bug was addressed and has since been merged.
Update 1.60.1: The update addresses these issues
This looks like an ongoing issue that is still not fixed in the current version (1.60.0).
This is now fixed in my current version (1.61.1).
On VSCode, if I needed a different terminal shell on a certain workspace, I had added the following setting in the workspace file (.code-workspace):
"settings": {
"terminal.integrated.shell.windows": "path\to\the\shell.exe"
}
After the latest update (April 2021 - version 1.56) this doesn't work anymore and I get this warning:
This is deprecated, use #terminal.integrated.defaultProfile.windows# instead
If I replace the setting name with the suggested one I get:
This setting can be applied only in application user settings
How can I set a different terminal shell per workspace?
Unfortunately, here is the same issue: https://github.com/microsoft/vscode/issues/123031 from https://github.com/microsoft/vscode/issues/123133.
Issue 123133 was closed 05/05/2021 with a temporary fix, see that issue and https://github.com/microsoft/vscode/commit/006591a7cfa31b9778e712b742b6e37f4afd0ed9. Here is my Insiders Build workspace settings file after the fix:
Note the previous error message is gone. I suspect that this "fix" will be in a point release to v1.56 fairly soon rather than waiting for v1.57.
As zendu pointed out, there's an open issue about it with a temporary fix:
A temporary fix was added to re-enable workspace shell settings when "terminal.integrated.allowWorkspaceConfiguration": true is set #122104
I tried it and it seems to work (at least for now).
I am developer behind a more clean Monokai Theme on VScode. [It is more of a simple hack.]
https://marketplace.visualstudio.com/items?itemName=Mit.Monokai-Polished
Whenever I release a minor update VScode doesn't delete older version from /extensions folder after reloading the window. How do I remove this bug.
My source code is for extension is available at this repo.
The older version will not be deleted if you just reload VSCode (clicking the Reload button in Extensions tab or using the Reload Window command. In order to really delete the older version, you need to Restart VSCode (close and reopen, all instances).
By the way, it appears to be designed this way, and not a bug. (related issue in VSCode repo).