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.
Related
My VSC shows the wavy underlines when something's wrong with my code, but does not display the hint overlay when I hover my mouse on it.
This happens whatever the language used (from CSS to Typescript) and whatever the type of irregularity (e.g. notice, warn, danger)
I'd say that's a setting I may have changed at some point, but can't find which one. Any idea?
More details:
I do have the message displayed in the Problems tab besides to the Terminal, but it forces me to switch from tab to tab ;
I do have other overlays like autocomplete/autosuggest ;
No extensions in my setup could have led to that situation (only a few installed, widely downloaded, nothing fancy or dodgy).
Actual behavior (nothing happens):
Expected behavior (from google images)
Go to File > Preferences > Settings.
Search for 'hover.enabled' (See below photo).
Toggle it.
If your editor still does not pick up the change, close all tabs, close all VSCode windows, and reopen it.
If it's still not working, try uninstalling VSCode and reinstalling it (make sure you don't have setting sync on).
Also, this question has been answered in at least one other place (Disable tooltip hint in Visual Studio Code)
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
I've encountered a very strange bug with Microsoft Visual Studio Code. I've been using VSCode for a few months now and never had this issue. When I open VSCode, the window just doesn't appear. The app is definitely open, because when I hover over the icon on my taskbar I can see what is being displayed in the app:
Unfortunately, when I click on it, the window does not appear.... I've uninstalled and reinstalled, deleted cache, tried older versions and nothing has worked. Has anyone else encountered this and fixed it? Any advice?
hover over VSCode icon in taskbar
right click on it
click on "New Window"
That should do it.
I had something similar. It appears that the window is just off-screen. I've used my DisplayFusion display manager - to move windows to center/top where I could handle it myself. I expect it'll also work using <Win> + <←> (maximize window to left side of screen).
In my case, the issue went away when uninstalling the GlassIt-VSC extension. I tried modifying the opacity of the window and then it disappeared. I highly suggest you try uninstalling this extension.
In my case I had connected HDMI cable but due to power off my monitor was off, but when I disconnected hdmi cable; VS code visible on my screen.
Got the answer since no one was helping.
Go to view.
Click solution explorer.
It should show the name of your project.
Click the small arrow at the beginning of the heading of your project.
Click source files.
Click yourproject.cpp.
Thank you.
I encountered a similar issue with a plugin called GlassIt while I was playing with a property called "glassit.alpha" somehow it went to 1 (possibly I changed it accidentally) and nothing showed up. (here's an image where you can slightly see that I set alpha to 20)
what i did was to just edit the %appdata%\..\Roaming\Code\User\Settings.json and set "glassit.alpha": 1, to 255
UPDATE I just realised there was already an answer I didn't see while I was writing this post
I had this issue during a remote desktop session and could bring the VSC window back via hitting F11 (via the onscreen keyboard in my case, since the F11 key on my keyboard was being captured by the host system).
In my case, I have a dual monitor setup, and the laptop was in clamshell mode. However, the laptop's built-in monitor was recognized as a third monitor, and VsCode was going there.
So when using Qt to build user interfaces, you all know that .ui files (forms) open in Designer mode by default, and that if you manually switch back to the Editor, then this message appears "This file can only be edited in Designer-mode".
Well, for some reason, and at some point, my file now opens BY DEFAULT in the editor, and the message does not show up. Worse, when manually switching to Designer mode, the main editing field is gray and empty and none of my stuff shows up ... Also no scroll bars or anything.
EDIT : actually, it is whichever form was loaded last that appears. And it is editable and all ... only the drop-down menu with the file name clearly indicates that it is MY file that is opened. When I perform an edit, then the edit is performed to this same last-opened form, and is reflected upon compiling. My display remains unchanged to the state that it had the last time that I was able to open it in the Designer.
EDIT : Also, along with the fact that my .ui file now opens by default in the Editor, it is also editable there like any other source file. But edits don't seem to bother, I modified some stuff or added gibberish, and it never showed after compiling nor did the compiler ever complaine ...
What's going on ? What did I do ? I have no crash nor any recent weird events to report ... It just suddenly started happening.
Thanks in advance for any clues,
Charles
It is very annoying to see that background around code is lighter then the rest of the program. When the cursor moves the highlighting moves up and down to full window width. Can you please propose solution how to turn this highlighting off. Same problem is in output of task log, and in file explorer.
I have deleted all the settings and Application data and I have same problem. I have installed vscode on windows and I do not have this problem with same settings.
Unfortunately this is an issue in Chromium. You can work around this by starting VS Code with --disable-gpu from the command line.
Sean
It appears this can be fixed for some users by selecting a different color profile in macOS display settings. Note that you have to change this separately for all monitors that you use.
For me, "Apple RGB" will show these blocks, and switching to "LED Cinema Display" or "iMac" solves the issue.
See also: https://github.com/Microsoft/vscode/issues/12473#issuecomment-269024219