-
Notifications
You must be signed in to change notification settings - Fork 30.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vscode auto imports behave weirdly after automatic package update #72539
Comments
Code action use the default operating system context menu (not a custom menu). However, on Linux you can configure to use custom rendered menus if you want. |
Please ask your question on StackOverflow. We have a great community over there. They have already answered thousands of questions and are happy to answer yours as well. See also our issue reporting guidelines. Happy Coding! |
Hi @jrieken ! Thanks for finding time to answer my question. |
Sorry, didn't find the name of setting, @sbatten will be able to help |
@Dar0n sorry for not getting this here sooner. The setting for modifying the titlebar and menus is |
@sbatten Oh my God, you made my day! The native menu was so ridiculously annoying! Last week was a nightmare! :) |
Hello there!
I am relatively new to Linux. Couple of days ago I have run some automatic update of all the packages with apt-get.
After that VSCode behaves somewhat weird. In particular, it suddenly forgot all installed extensions (had to install them again). But the most bothering issue is with auto import(ctrl + .): instead of themed colorful suggestion list with automatic selection of the most probable option, I get a "default" white list with no selection, that occasionally disappears while I navigate through it.
I tried to install older version of VSCode from couple of months ago, but that didn't change anything.
I also tried to delete ~/.vscode folder, but that also didn't do anything.
I failed to find similar issue and not sure where even to start to dig.
Environment:
Kubuntu 18.04, VSCode 1.29.1, Typescript 3.1.4
The text was updated successfully, but these errors were encountered: