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.
Related
Example of breakpoints in VS code
I’ve tried to use use this instead of commenting out sections, running it and seeing the difference but it doesn’t seem to apply.
I’ve read this article https://learn.microsoft.com/en-us/visualstudio/debugger/using-breakpoints?view=vs-2022 but if it could be explained in a different way it would be helpful. Thanks.
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..!
Dear Fellow Asciidoc/VSCode users!
I've recently switched to Windows from Linux. It is true I have not updated my Linux VSCode or any extensions for a few years now, because it worked as I wanted and didn't want any new features to brick anything. So, my issue might not be os-release-related, but rather version-related.
In .adoc files, I cannot seem to be able to enable word/snippet suggestions. Some code suggestions work, but not my snippets and simple text suggestions from one or more currently opened files. This worked on my old setup.
Enabling suggestions with editor.wordBasedSuggestions, editor.suggest.showWords: true, editor.snippetSuggestions, or the other related settings options I was able to find does nothing, even after reloading the editor.
Suggestions work normally in .txt and .py files for example.
While I didn't find anything online on how to enable suggestions, I did find a lot of posts where people wanted to disable word suggesting and also failing to do so using the above-noted settings options.
I must be missing something. Could it be a language-configuration issue? I couldn't find any relevant settings here: Language Configuration Guide.
Could it be related to something else in the AsciiDoc language extension?
Any ideas? Thanks a lot.
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.
Syntax highlighting looks like this:
It happens not only on my Mac, but also on my colleague's Mac.
Is there a way to fix this issue?
I am having this same issue. A temporary fix is to go to another file and then back to the original file in the editor. This will reset the highlighting and make it a little bit more bearable.
Submit a bug report at Apple's Bug Reporting Site.
Certainly annoying, though.