I know that a similar was asked on Intellisense not working golang test files, but since I am new to VS Code I didn't quite understand the solution. Also since I have a low reputation I couldn't comment for help.
What I know about my problem is that on Ctrl + Space VSCode used to show the list of functions associated with the Golang package, but suddenly one day it stopped working.
Okay, I found out my answer. Apparently for some reason in my settings.json the line "go.useLanguageServer": true, wasn't there. After adding it VSCode told me to install something called gopls which fixed everything.
Related
fmt.Printf("hello") was working great with intellisense
but suddenly in every go file my fmt.P .. suggestion becomes this
and this
I am not getting "fmt.Printf()" suggestions anymore and getting stuck with those "const", "func", "import", "type", & "var".. what is happening? (Though it is not suggesting fmt.Printf() but it's still working). how can I get normal suggestions by intellisense like previous?
I tried disabling GO official extension, then it got fixed but also I lose all autocomplete/suggestion feature. a go file in root directory is working fine but other files inside packages are showing this kinda problems. Please help
After searching a lot I couldn't find exact problem and solution. And somehow I saw some were facing "case-insensitive import collision:" and it was due to upper-case and lower-case mixture usage in filename. I remembered it seeing in my package name (though this error vanishes sometimes and ignored it as code execution was working) and tried renaming my filename from "sequenceUtils.go" to "sequence_utils.go" and boom ..! intellisense started working ..! though my colleague was working with same filename and he wasn't facing problems..
I think the problem should be properly identified..!
I'm having issues with my integrated terminal in vs code. It has multiple cursors in weird placed when inputing text. I have tried reinstalling vs code and the issue wasn't solved. I also tried modifying the settings.json which also didn't help. I will appreciate any help given.
Microsoft Visual Studio Community 2019
Using C#, this is about what appears in the light bulb tips...
I used to be offered a Quick Action (QA) to fix the format, but that QA no long appears.
For example, a QA used to appear when I had no spacing around binary operators, like this:
if (File.Exists(subsFile)&&(subsFile.Length>5))
It would correct to:
if (File.Exists(subsFile) && (subsFile.Length > 5))
The problem started when I clicked on a QA that I was curious about (but I cannot remember what it was). I assumed there would be a simple way to undo whatever effect it had, but I was wrong.
If I do Ctrl-K Ctrl-D, then the line would be corrected as above.
I have checked the options in the Tools>Options... menu, and the spacing seems to be correct.
I have looked carefully through the Code Styles options, but nothing seems to apply.
I have searched the web at length, including Microsoft and, of course, stackoverflow, and found nothing to help.
It is annoying that I cannot use a feature supplied by Microsoft to help novices like me.
Can anyone help, please?
Solved: Not a serious problem, but it annoyed me so much that I ran Visual Studio Installer and chose the Repair option. (It's on the Start menu in Windows 10.) This didn't solve the problem on its own, and may not have been necessary for the solution.
Next I had a look at the file .editorconfig (found in Solution Explorer). Previously when I considered this, it seemed to entail a huge learning overhead, and it scared me off, but this time I spotted this line in the file:
dotnet_analyzer_diagnostic.category-Style.severity = none
When I changed this to:
dotnet_analyzer_diagnostic.category-Style.severity = severity
and saved the file, the problem went away like magic.
I don't know enough to explain why this worked.
I have a single project in VSCode where breakpoints are not working and I can't figure out why. I'm new to VSCode but I've got them to work in other projects (Pascal) but there's something about this one it doesn't like.
Does anyone at least know what this means when the break points are gray like this? Is it a bug? In the 2nd screenshot you can see I can run LLDB from the terminal on the same executable so it's not LLDB messing up.
This might be an obvious answer, but it's what solved the issue for me when I encountered it.
Recompile the program and try again
I've had this problem for a long time. At some point IntelliSense just stopped working on my laptop, completely. Whenever I type in a ., -> or (, it says
IntelliSense: 'No additional information available' (See 'Troubleshooting IntelliSense in C++ Projects' for further help.)
It doesn't work in any projects, even if I make a new blank one. Hovering over identifiers doesn't show any information either. Furthermore, some actions such as go to definition used to completely freeze the studio, until I did a full settings reset and that problem was resolved. But intellisense is still not working. Is there anything I can do, short of full reinstall? (If that would even help.. besides I doubt I can find the CD now.)
Update: this question describes the exact issue I was having: VS2010 Intellisense problems
Since I already tried installing service packs and something didn't go right, I went with a rather hacky solution - I replaced my ole32.dll with an older version, which seems to have fixed the issue. This is obviously not recommended if you care about your system's stability, but if you're still running WinXP, chances are that you don't ;)