Fix vscode intellisense engine to 'Tag Parser' #4381
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
janjongboom
force-pushed
the
vscode-intellisense-engine
branch
from
5631be6 to
1b0d7ee
Compare
janjongboom
changed the title
|
@janjongboom Thanks for the simple patch! |
theotherjimmy
approved these changes
May 24, 2017
|
Just 'cause. /morph export-bulid |
|
/morph export-build |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
Outputmbed Build Number: 43 All exports and builds passed! |
|
thanks @janjongboom! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since the vscode C++ plugin has been upgraded to 0.11 the intellisense engine has changed, and it does not understand the mbed code base.
Quick fix is to set the engine back to the previous engine.
See https://github.com/Microsoft/vscode-cpptools/blob/master/Documentation/LanguageServer/FAQ.md#what-is-the-difference-between-includepath-and-browsepath-in-c_cpp_propertiesjson
Need a proper patch though, created #4380 as a follow up.
@sg- @theotherjimmy