It looks like this issue was introduced in v1.26.0 a few days ago. If you don’t use Ctrl+P to navigate in the filepicker, you can disable or change the vim shortcut back to the default VSCode behavior, as noted in the issue: // keybindings.json { “key”: “ctrl+p”, “command”: “workbench.action.quickOpen” }
On the Mac, use the Command + . keys to pop up a menu of Quick Fix suggestions. On Windows, use the Ctrl + . keys. Then just select the Quick Fix suggestion that you want to apply to your code. Example on the Mac:
If I understand correctly, try unchecking Settings > Text Editor > Glyph Margin.
You can use the command palette: Menu: View > Command Palette… (or F1) Search: “Workspaces: Remove Folder from Workspace…” and select the folder you want to remove. Hope this may help you
Just create a .prettierignore file in the project with ** The entire codebase will be ignored for Prettier plugin.
This extension allows you to open a folder in a new vscode window. Open Folder Context Menus for VS Code
Currently there is no extension for VSCode that does that, it may possible though see: issue. A good starting point will be to use something like: LaTeX Workshop’s preview to display/overlay them over comments or something like that.
I had a similar problem today, I got the error “The container does not meet all the requirements of the VSCode Server”. Apparently, it’s because in version 1.86 they changed the linux requirements for the remote server Starting with VS Code release 1.86, the minimum requirements for the build toolchain of the remote server were … Read more
I had the same issue. My preview started working right after I installed the Java Runtime Environment (JRE).
It looks like this is an issue many people have had for a while, and the solution is to do the following (original source): Open up your user settings. On windows the shortcut is CTRL + , Search for vim.foldfix and check the checkbox so the setting is set to true. Alternatively, open your settings.json … Read more