microsoft / microsoft/vscode-cpptools
Don't override sticky scroll settings if intellisense is disabled, to avoid conflicts with Clangd
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Environment
- OS and Version: Windows 10
- VS Code Version: 1.99.3
- C/C++ Extension Version: 1.25.3
- If using SSH remote, specify OS of remote machine: No SSH
Bug Summary and Steps to Reproduce
Refer to https://github.com/clangd/clangd/issues/2221
When both Clangd and the Micosoft's C/C++ extension are installed, the latter messes with the sticky scroll settings, prevending Clangd from displaying it properly.
This happens even with "C_Cpp.intelliSenseEngine": "disabled", which is probably undesirable.
I suggest disabling this behavior when intellisense is disabled.
How to repro:
- Install both the MS C/C++ extension and Clangd. Ensure Clangd is working.
- Disable intellisense when prompted (MS extension suggests this when it sees clangd).
- Trigger sticky scroll. Ensure that you follow the style where
{s are on separate lines. - Observe that the sticky scroll only displays the
{s instead of the function signatures:
Configuration and Logs
Not relevant.
Other Extensions
No response
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the conflict with the Microsoft C/C++ extension and Clangd on Windows using the reported IntelliSense-disabled configuration, then trace the extension's sticky-scroll settings handling. Done means the C/C++ extension no longer overrides sticky-scroll behavior when IntelliSense is disabled, while normal IntelliSense behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100