Currently on Ubuntu I'm running KDE version 5.18.8, and I've just started coding in Visual Studio Code, but when toggling the console, I just get an old notification on the top right corner of my screen informing me how old it is, not using the shortcut entirely.
*(I toggled the terminal manually in the settings)
Is this a shortcut I have to change in vscode or KDE? Since there isn't anything online I can seem to find for this. It's a bit of an annoyance.
Related
I installed Visual Studio Code 32 bit version (1.71.1) on a Windows 7 machine. I checked the box that said to launch it after I click Finish. The "wait" mouse cursor showed for a second or two, then nothing.
I tried double clicking the desktop icon with the same results. No error message. Not indication that it attempted to start. I did change the desktop icon to "Run as administrator" and that got me the prompt to allow changes to the system, but again, nothing comes up.
Any idea of what is going on? Is there a specific .NET version I need to have?
I have installed vscode on my ubuntu machine.
Opening it up and choosing Terminal -> New terminal opens up an integrated terminal. However, there is just a white marker where the working directory should be, and it is completely unresponsive. I have read the vscode troubleshooting and search here, but can find anything about it. What is wrong? See image of unresponsive terminal below.
I often clear the terminal on macOS with CMD-K (sort of equivalent to reset). When I use the terminal in Visual Studio Code and I press CMD-K, the banner at the bottom of the screen shows "(CMD-K) was pressed. Waiting for second key of chord..."
How can I make CMD-K pass through the editor to go to the terminal in Visual Studio Code?
I have occasionally run into this bug (VS Code on MacOS) and each time it randomly would fix itself until recently it kept persisting even through restarting my laptop. I have now found that closing all open projects seems to fix this issue for me.
Might be related to how VS Code stores your current workspace state (opened projects and file modifications). It seems maybe these state settings sometimes get corrupted somehow 🤔
I was getting black screen after opening Visual studio each time. I got a solution from Stack overflow i.e code --disable-gpu. It is working fine but my main issue is when I use to code in vs code. I am not getting suggestions as intellisense is not working and I am unable to install any extensions from Visual studio code.
to disable hardware acceleration permanently (without adding --disable-gpu argument) open folder "C:\Users\your_username_here\.vscode" than open file argv.json with any editor and look for
"//disable-hardware-acceleration": true, and just remove the tow slashes before disable. i think there is a similar workaround in linux
Hit Ctrl Shift P to open the command palette,
Type Developer and choose Developer: Toggle Developer Tools.
switch to the Network tab in Dev tools.
Search for extensions now
Go to properties of visual studio
change target . Add --disable-gpu
make sure to add a space before --
it will resolve your issue.
I recently updated Visual Studio Code to a new version (1.7.2) on my Mac.
I am used to open different 'windows' of VS Code at the same time on different projects.
In previous versions of VS Code I could navigate the VS Code open windows via 'cmd+>' (or 'cmd+z', now I do not remember this exaclty).
Now this key combination does not work anymore and, to navigate windows, I need to open the 'Window' menu option and chose from there.
Does anybody know how to navigate among open VS Code open windows on Mac with this version of VS Code?
Thanks in advance
control+w is working for me
It is showing all active windows
cmd+< is not provided by VSCode, it's a global shortcut of OSX witch works for all applications with multiple windows. You can check if its properly set up in Preferences->Keyboard->Shortcuts
However, there is a command in VSCode to select open windows from a list. Search the command palette for Switch Window, you can bind it to a shortcut yourself, command is called workbench.action.switchWindow.