microsoft / microsoft/vscode-cpptools
Intellisense doesn't work on windows case sensitive folders
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: win11
- VS Code Version: latest >= 1.80
- C/C++ Extension Version: latest (2024-3-22
There is already an existing issue: https://github.com/Microsoft/vscode-cpptools/issues/1994
and a pre-release version: https://github.com/microsoft/vscode-cpptools/releases/tag/v1.13.0
unfortunately it looks abandoned as it is more than 1 year with no progress and still in pre-release version.
especially as my cpptool plugin is newer than that pre-release version
Bug Summary and Steps to Reproduce
Bug Summary:
intellisense doesn'twork on windows with NTFS case sensitive attribute enabled
Steps to reproduce:
- enable case sensitive in a folder
- write some cpp code in that and use vscode cpp tools
- intellisense is just broken
Expected behavior:
it should work instead.
Configuration and Logs
.
Other Extensions
No response
Additional context
is there anything that can be done without switching to a pre-release version that is older than 1 year in respect of the latest one?
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
Start by reproducing the failure using the reported Windows 11 setup: enable NTFS case sensitivity on a folder and run C/C++ IntelliSense there. Read existing issue #1994 and compare the current extension with the referenced pre-release; done means IntelliSense works in a case-sensitive folder without requiring that older release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100