Open jacobdufault opened 6 years ago
What is good to bring along with this change is a clear description of how this project is different to MS C/C++ extension so that a user knows each extension's strong and weak points and could have a better idea which of two could be a better match to her needs. Could you please add something along the lines to the README? I'm not sure my request could be labeled good first issue
because I think the author should know better about the differences.
Should be documented in https://github.com/jacobdufault/cquery/wiki/Visual-Studio-Code
This is not an obvious issue to the user, and I do not expect users will read docs.
It would be very rude to pop up something telling the user "you should disable the official plugin, otherwise xxx"
I think a broken experience is worse than being rude, though I agree being rude is not good. The statement can be worded to not sound offensive, but ultimately I'd like to submit a PR to the C++ extension which allows indexing to be disabled, and then tell the user they should disable C++ indexing.
I'm totally pro such a "warning" if this causes problems. But most important, the documentation should explain how to replace the Microsoft extension with something equivalent, e.g. what do I need to install to debug just as with cpptools?
You can use https://github.com/WebFreak001/code-debug. I'm not sure how well it works in comparison to cpptools.
I just did a quick test, and no, this extension is no real alternative to cpptools. Also code formatting doesn't work anymore when disabling cpptools :-(
We should probably send a PR to cpptools then to add a setting to disable indexing.
Warn user to disable Microsoft C/C++ extension if they have it enabled via a notification in vscode or similar.
When both are enabled there are confusing errors, ie, goto definition gets very slow. Native code debug and clang format are available in separate extensions outside of the Microsoft C/C++ one.