All of a sudden, I am facing this problem in my VS Code editor. If you look at the first picture, that is a code snipped of my VUE 3 project. Where ever I am clicking in the picture, the cursor is not appearing.
This is the same file with the other section, where the cursor seems to be fine. Its works smoothly...
Does anyone have any idea about this issue??
I also checked in Stack Overflow, some issues suggested reinstalling the VIM extension, whereas I don't have VIM installed in my docker environment.
Related
I have a user snippet configured in Visual Studio Code. Let's take one of the items in this snippet: one with the prefix imp.
Now, prior to the recent VSCode update, as soon as I did something like the following.
it automatically showed the autocompletion box to me (I didn't have to press Ctrl + Space to activate it), as shown below:
But now after the update, something strange has happened. When I type in just im, obviously, it shows me the <img> autocompletion suggestions as shown below:
But when I continue to type the full thing imp, the autocompletion box gets hidden. It's only when I press Ctrl + Space that I get the autocompletion box again.
What is the reason for this problem and how to fix it?
I can reproduce your issue exactly, which led me to look to see if it has been reported on github. It has, see Snippets gone from IntelliSense.
From same issue as above:
I have pushed a fix for next insiders and I have pitched this for the
1.75.1 recovery release
It is in today's Insiders (I just tested it) 02/03/2023.
So you can either try the Insiders Build now or wait for the Recovery Release. And continue to use the manual trigger of Ctrl+Space in the meantime.
As #WayneBloss mentions in a comment below, disabling the snippetsPreventQuickSuggestions setting might fix the issue.
I encounter the "Save" and "Save As" menu items greyed out randomly and regularly while editing files in VS Code. Been happening for a few years. Most of the time it's while I'm editing Golang code but it has happened for other file types. If I click on the x to the right of the file name tab for the open file, I then get the option to save the file. Ditto if I try and close VS Code.
So VS Code knows there are unsaved changes. Closing VS Code completely and restarting it "fixes" the issue until the next time. Did a search and I don't see any "recent" issues like this that others have experienced. Running on macOS. Happened under Big Sur, Monterey and now on Ventura. Currently running VS Code 1.72.2. I tried to narrow it down by disabling some extensions but it still happens.
Tried removing extensions. Still happens. Uninstalled and re-installed VS Code.
Lately when using Jupyter Notebook in VS Code to write some assignments for my studies I ran into a quite annoying problem - whenever there is a mistake in my code cell that prevents it from running, the "traceback" (or however you call it) to the place where the error persists is colored with a high-contrast marker (the color depends on the theme used) and makes the content pretty much invisible unless you manually "select" it with the mouse coursor. Is there any way I could fix it without going too much in-depth into VSCode/Jupyter Notebook extension settings?
The highlighting looks like shown below.
Yellow syntax marker problem.
And another one here.
I tried all the themes preinstalled with VS Code such as Monokai, Solarized Light etc., and also a custom theme of my choice called Dracula.
Thanks in advance.
This issue has recently reappeared. While the issue is being fixed you can change the highlight colour within the vscode settings.
Open settings and search for "Workbench:ColorCustomizations"
Image of settings page
Create or alter the "terminal.ansiYellow": "#eed202" to a more appropriate value like "terminal.ansiYellow": "#9b4550". See the linked image.
Credit for this fix: https://github.com/microsoft/vscode-jupyter/issues/8717#issuecomment-1241776226
I also have this problem. It looks like they fixed it less than 1 month ago as of writing this, so it may go away if you update to a recent pre-release of Jupyter in VS Code. Personally, I am going to live with it until the next stable release.
My version of Jupyter in VS Code:
Screenshot of Jupyter Versions
Screenshot of vscode-jupyter github: Screenshot of vscode-jupyter github
https://github.com/microsoft/vscode-jupyter/issues/8697
All of a sudden my viewer would not pop up anymore whithout me changing anything in any options.
F7 view and ctrl+leftmouse work alright but when I re-build, the viewer wouldn't scroll to the current editing position.
I reinstalled but it seems that the configuration file remained.B&V settings
Attached my settings, only focus is added in default viewer.
I found the problem:
There was this C_aus_IVT_RK in the code below which provoked the following error:
**Missing $ inserted. ...gnorespaces C_aus_IVT_RK}}{67}{figure.12.7}
**
The compiler seemed to dislike the underscores.
Funny enough the pdf was compiled though.
\begin{figure}[h]
\centering
\includegraphics[width=0.7\linewidth]{../TexS_FigVerz/C_aus_IVT_RK}
\caption[C_aus_IVT_RK]{Captain Caption}
\label{fig:C_aus_IVT_RK}
\end{figure}
Now, everything works alright.
I am trying to navigate to the explorer window via Ctrl+Shift+e but this sequence of keystrokes is not recognizable by VSCode 1.55.2.
I checked this two ways. First, via trying to check what Ctrl+Shift+w and Ctrl+Shift+e were binded to via keyboard shortcuts (Ctrlk, Ctrls) and then recording the keystrokes to reveal what they were binded to.
You will observe that ctrl+shift+w is recognized. Then, in the gif, when I press ctrl+shift+e it renders as ctrl+shift+unknown.
Then, whenever in a saved open file in the editor, when I press ctrl+shift+e hoping that the explorer navigator opens up on the left, that does not happen. Instead the file becomes unsaved with an underscore e appearing in the file.
This is completely new and strange behavior of the editor. I did not encounter this before.
Any help is appreciated.
Edited to add update: VSCode folks indicate that this is a known issue. Ctrl+shift+e translates into insertion of an emoji, it seems. See their comment here.
Same thing happened to me, using linux (ubuntu).
I installed it from the snap store, and tried reinstalling from there and the problem was still there.
Uninstalled and installed it manually from de .deb package at their webpage and it was solved.
Maybe it's an issue they have solved in the latest version (1.15.8) but it's still unsolved in the snap version (1.15.2 in your case, i didn't pay attention on what was my version).
Same problem. Installing vscode from .tar.gz - works perfectly fine, installing from snap leads to unexpected behaviour on Ctrl+Shift+E