relationship between browse.path and tag parsing #13075
Unanswered
jalanh11640
asked this question in
Q&A
Replies: 1 comment 1 reply
-
Yes, setting browse.path to ${workspaceFolder} should be recursively tag parsing the source files in there. If you set C_Cpp.loggingLevel to "Debug" you should see "Processing folder (recursive):" with your workspace folder root. I'm not sure why that wouldn't be happening...maybe logging could help explain it? You can prevent tag parsing by setting C_Cpp.files.exclude to some glob pattern that matches the folder such as "C_Cpp.files.exclude": {
"**/test": true
}, |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi, I'm running into a problem where I don't see intellisense tag parsing a lot of my source files.
I'm running inside a dev container with cpptools v1.22.11 and vscode version 1.95.3. I have a "browse" configuration of the following.
With this setting, the only 'tag parsing file' lines I see in the C/C++ debug output are header files found underneath the compiler directory.
If I change the path to "${workspaceFolder}/**/*" then all my sources get parsed by the tag parser.
This seems to be reverse of what the browse.path help text indicates.
On a slightly different subject, is there a way to prevent tag parsing of some files in a given configuration? For example, I have a configuration called 'release'. In this configuration, I would like to ignore unit test files in '${workspaceFolder}/**/test/'.
Thanks,
Jeff
Beta Was this translation helpful? Give feedback.
All reactions