Sean McManus

Failed to initialize vscode-spotify. We'll keep trying every 20 seconds.

2

VS Code 1.5.3. Spotify 1.0.0. Win10. I can't get this extension to work. On launching VS Code, it just gives "Failed to initialize vscode-spotify. We'll keep trying every 20 seconds."....

Repros after selecting the "return 0;" and using Ctrl+Shift+R Ctrl+E. ```cpp int func() { return 0; } ``` Doesn't repro after 2 new lines are added to the top of...

The 'Add #include' code action incorrectly uses "../" instead of <> when an includePath is used that is lexicographically less than the source file's parent directory

1

See the 2 screenshots: If the includePath has "${workspaceFolder}/a" then the bug repros, but with "${workspaceFolder}/t" it behaves correctly -- t is lexicographically greater than the source's parent directory "sub"....

See the screenshot -- test2 is on the includePath and the current file is at the root, so it should be suggesting `` since file.h is not in the same...

Incorrect "Unable to process IntelliSense for file with same canonicalized path as existing file." message can appear when cpptools crashes

7

Kill cpptools on Mac or maybe other Linux OS's. It don't think it repros on Windows. Bug: An incorrect warning appears: LSP: (invoked) textDocument/didOpen: file:///Users/user/test1/test4.h Unable to process IntelliSense for...

We only send IntelliSense a single list of include paths instead of separate "quote" and "system" paths. Repro is like ```cpp #include int main() { std::string s; return 0; }...

IntelliSense squiggles don't update correctly after an edit and cursor line change or save

1

Use code ```cpp void func() { std::vector a; } ``` Add `#include ` via typing, pasting, or the Add include code action. Afterwards, move the cursor to a new line...

Switch to using setTextDocumentLanguage instead of adding to files.associations

18

The Septemember 2018 release added vscode.languages.setTextDocumentLanguage, so our extension can try using that instead of adding files to files.associations. The previous thread is https://github.com/microsoft/vscode-cpptools/issues/722 .