When I was watching a VSC tutorial I noticed an interface overview feature, what I understood it as was that it acted as a small helper, so that when you hovered over something it would give an explanation of what is does, I may be wrong. But, when I reopened VSC th option didn't apear anymore as it did when I first opened thee application.
Related
I'm using this Cobol extension for Visual Studio Code: https://marketplace.visualstudio.com/items?itemName=bitlang.cobol
It works very well and I've got it all set up. The only problem remaining is that I want to use the functionality to press F12 to jump to a definition in my code, so if I click "styledocument.sd" in the code of a program and press F12 it's supposed to open the styledocument file, but all the editor does is say "No definitions found for "styledocument"." Our lead developer says the functionality used to be there and it just vanished at some point for no reason.
Is there any way to get this functionality back? It'd be really useful, I'm very new at programming and this would be a godsend as it'd help me find my way around the code at a reasonable pace, as everything seems really difficult right now.
Thank you everyone for your replies!
I've recently moved to Visual Studio Code from Sublime Text.
Something that I'm missing is the "automatic preview mode" (I don't know the exact name): in ST, if I navigate the files in the sidebar with the keyboard, every file is automatically opened in a (static) preview editor.
I couldn't find anything similar in VSC. The most similar functionality requires me to single-click, but I have two problems with this:
I'm a "keyboard-prevalent" user, and (single-)clicking defeats the purpose;
in ST this happens automatically, so it's faster anyway.
Am I missing something?
I've been searching for a while, but can't find anything relevant. It seems there are references to this functionality from Search Files (Ctrl+P), but I'm looking this functionality on the sidebar, since I use this while working on files of a single directory.
Can anyone explain these three debug symbols on VSCode I have found on the internet?
My vs code has the one with the play icon.
All demos online on debugging have the one in the middle. How do I get that?
Also, node js debugging is installed but I think it shows as disabled, with no option I can find to enable it.
To answer your question directly [TL;DR]: you already have it if you are using the latest version of vscode. It will take you to the same view as the one on the right
If you look at the codicon libray ref the middle one you pointed out is not present.
Visual Studio Code made changes in February 2020 ref that incorporates running and debugging to be something more harmonious:
User studies revealed that new users have difficulties finding how to run their programs in VS Code. One reason is that the existing "Debugging" functionality is not something that they relate to "Running" a program. For that reason, we are making "Run" more prominent in the UI.
The main menu Debug has become the Run menu.
The Run and Debug view has become the Run view and the corresponding Activity Bar icon now shows a large "Play" icon with a small "bug" decoration.
So in other words, there is no difference. The 'Run' and 'Debug' view is synonymous and the icon reflects those changes. As they noted, the Debug view is now called the 'Run' view, but it still offers debugging and breakpoints.
There are 2 possibilities you are running into however:
The tutorials and guides you are using are out-dated (showing an outdated version of vscode)
The tutorial or guide is using an extension that offers debugging capabilities. Extensions have some control over the icon you see
The extension is for single file debugging, according to the June 2020 ref notes, vscode recommends the following:
For debug extensions that want to improve the single file debug experience by adding a "Run" and/or "Debug" button to the editor, we recommend following these guidelines for a consistent look and feel:
Contribute Run and/or Debug commands in the package.json (see Mock Debug):
Use the command titles "Run File"/"Debug File" or "Run Python File"/"Debug Python File".
Use the $(play) icon for Run and $(debug-alt-small) for Debug.
Where their codicon library was updated in June to reflect the following:
As you can see, none of them are prefixed with verbiage like 'run', but they all represent the same functionality.
Additionally, you may see this icon as well:
This represents the panel (view) where the output of your debug will go.
UPDATE: I solved my own problem. Solution is at end of this post
Original Post:
Intro:
Hi, I had Visual Studio Code (VSCode) installed a long time back for use with Unity but ended up not using it and opted for Visual Studio instead because that was what my Unity course was using.
I am now learning HTML so I now want to use the Visual Studio Code as the editor.
Problem:
When I type out my HTML code, VSCode is not autocompleting any of my code or giving me any suggestions or colour coding the text.
Troubleshooting steps done:
I completely uninstalled Visual Studio Code including the user data folders: .vscode in users and Code in Appdata/Romaning (which were advised on the visual Studio code website uninstall instructions).
I then installed a fresh version. But the same problem persists.
Update: I have learnt that the feature that I have an issue with is called Intellisense. CTRL-SHIFT-R is supposed to refresh this feature module. So did this and I get the message "No refactorings available". So perhaps I am missing a module or plugin that I am supposed to also install?
I'd appreciate someone's help to solve this.
Many thanks.
PS This is my first StackOverflow question, I hope it's not a forehead slapping debut!
UPDATE: SOLUTION
I just solved my own problem...and it's probably a beginner's mistake...
I discovered at the bottom right corner of the editor, this a menu tray. One of these items showed "Plain Text". On clicking it, it showed a list of programming languages. Naturally HTML was one of them and I upon clicking it. The editor Intellisense auto completion, suggestions etc kicked in.
If I may comment, I wonder why this element is somewhat conspicuous. It's not obvious for a beginner to know to click on "Plain Text" at the bottom right corner without scouring the interface or try to find a third party tutorial video. Perhaps, I can give that as a feedback to the developers.
I just solved my own problem...and it's probably a beginner's mistake.
I discovered at the bottom right corner of the editor, this a menu tray. One of these items showed "Plain Text". On clicking it, it showed a list of programming languages. Naturally HTML was one of them and I upon clicking it. The editor Intellisense auto completion, suggestions etc kicked in.
Visual Studio 2015 does not have a way to only select IntelliSense when I press Enter or Tab anymore in C# for 2015. It's available for JavaScript but not C#.
I'm trying to create a MEF project and hook into the IntelliSense to change this behaviour for C# files. Just to get started, I tried to implement this sample plugin from Microsoft:
https://msdn.microsoft.com/en-us/library/ee372314.aspx
The sample compiles, but it does not work. Nothing in the code is triggered from the debugged IDE. The samples tells to start a new text file and press "a" to get demo IntelliSense, but it never trigger.
Here's the code project if anyone want to look into it:
http://ontime.zdata.no/donwload/ProperIntellisense.zip
Could someone guide me in the right direction here, the documentation in this area is very fluid.
There isn't a supported way to use the APIs to customize this. The behavior you're looking to change falls under the Roslyn project on GitHub so you're more than welcome to file a bug there as feedback. You're also welcome to send a pull request, but at this point it's really tricky to make a change to the editor components of Roslyn and apply those to your locally installed Visual Studio. It's something we're working on fixing but it's not done yet.
The workaround is to press Ctrl+Alt+Space when inside the editor. That will toggle into the correct IntelliSense behaviour. Not a very easy thing to find, but it saved my day. They should probably give better information about this toggle feature, and make it more visible.. Still, it will not be remembered after closing the IDE, so you have to do it every time you start the IDE.