Re: Need some help with Visual Studio Code

So in your title you mention VS Code, but in your post you talk about VS, so I am not sure which you mean. VS is the heavyweight IDE and VS code is a lightweight code editor. I will just assume you use VS code as thats what I use, so that I can write about.

Navigating to the next problem/error/warning is bound to alt + f8 by default. When you press that your focus will jump to the description of the problem. this is outside of the editing field. after reading the description, you can go back to the editing field by pressing shift + E on NVDA and pressing spacebar to focus on it. Your editing caret inside will have jumped to the line where the problem is.

One important thing to note is that for problems to be detected you need the appropriate language support. Usually when you start editing a source file, if you dont have the recommended extension for it, VS code will alert you and you can download and install it directly from VS code.

I just checked on my machine and code linting definitely works as described for Java. I tried C as well, but there the linting doesnt seem to work for some reason, although other features like autocompletion work fine...

I use the recommended extension packs for both.

I have had really good experiences with VS code especially when it comes to autocompletion. Note that It is written and natively supports TypeScript/_javascript_ so that's where you get the richest support, but support for other languages is also generally excellent.

-- 
Audiogames-reflector mailing list
Audiogames-reflector@sabahattin-gucukoglu.com
https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
  • ... AudioGames . net Forum — Developers room : ricardo0922 via Audiogames-reflector
    • ... AudioGames . net Forum — Developers room : Guitarman via Audiogames-reflector
    • ... AudioGames . net Forum — Developers room : nuno69 via Audiogames-reflector
    • ... AudioGames . net Forum — Developers room : Dragonlee via Audiogames-reflector

Reply via email to