Skip to content

0.20.0

Compare
Choose a tag to compare
@sean-mcmanus sean-mcmanus released this 30 Oct 23:18
· 2680 commits to release since this release
0cf237c
  • Add IntegratedTerminal support for Linux and Windows. #35
  • Unify Visual Studio Code debug protocol parsing by using a shared library with Visual Studio.
  • Fix IntelliSense-based Go to Definition on overloads (in the same TU). #1071
  • Fix inactive regions not being disabled when falling back to the Tag Parser. #2181
  • Fix #include completion not working with compile_commands.json or custom configuration providers. #2242
  • Fix IntelliSense failing if recursive includes removes all paths. #2442
  • Fix incorrect IntelliSense errors with MinGW (stop using -fms-extensions by default). #2443, #2623
  • Fix error squiggles sometimes not updating after typing. #2448
  • Add support for Mac framework paths in compile_commands.json. #2508
  • Fix IntelliSense-based Go to Definition falling back to the Tag Parser for definitions not in the TU. #2536, #2677
  • Fix IntelliSense-based Go to Definition on the identifier of a definition with no declaration. #2573
  • Fix IntelliSense-based Go to Definition not falling back to the declaration (in certain cases). #2574
  • Fix IntelliSense-based Go to Definition going to the wrong location after edits are made. #2579
  • Fix Go to Definition when the intelliSenseEngineFallback is Disabled and #includes are missing. #2583
  • Fix empty C_Cpp.default.* settings not being used. #2584
  • Fix quoting around ssh's command (for the debugger). #2585
  • Fix crash on hover (and Go to Definition) when using the Tag Parser. #2586
  • Fix errors when a workspace folder isn't open. #2613, #2691
  • Fix -isystem without a space after getting ignored in compile_comamands.json. #2629
  • Fix Insiders update channel installation bugs. #2636, #2685
  • Fix IntelliSense-based Go to Declaration falling back to the Tag Parser if the definition is also in the TU. #2642
  • Fix the Disabled intelliSenseEngine setting not working with custom configuration providers. #2656

Instructions

To use the "offline" .vsix (that doesn't download dependencies on extension activation), download the .vsix that matches your OS and run the "Install from VSIX" command in VS Code.