Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect warning "Path is not a directory" #5314

Closed
Richhoef opened this issue Apr 16, 2020 · 1 comment · Fixed by #5320
Closed

Incorrect warning "Path is not a directory" #5314

Richhoef opened this issue Apr 16, 2020 · 1 comment · Fixed by #5320
Labels
bug Feature: Configuration An issue related to configuring the extension or IntelliSense fixed Check the Milestone for the release in which the fix is or will be available. Language Service quick fix
Milestone

Comments

@Richhoef
Copy link

Type: LanguageService

Describe the bug

  • OS and Version: Microsoft Windows [Version 10.0.18363.752]
  • VS Code Version: 1.44.1
  • C/C++ Extension Version: 2.27.0
    When I want to use the env section in c_cpp_properties, I get yellow squiggles under the paths at the default_forcedInclude saying "Path is not a directory". Although this is true, it is also completely irrelevant. The forcedInclude is ment to be a file (at least, in my case it is).

Steps to reproduce

Here is my c_cpp_properties.json:

{
   "env": {
       "default_includePath": [
         "${workspaceFolder}/some_path",
         "${workspaceFolder}/some_other_path"
       ],
       "default_defines": [
           "some_defines",
           "some_other_defines"
       ],
       "default_defines2": [
           "some_more_defines",
           "some_more_other_defines"
       ],
       "default_forcedInclude": [
           "${workspaceFolder}/some_path/some_file.h",
           "${workspaceFolder}/some_path/some_file.c"
        ],
        "default_browsepath": [
           "${workspaceFolder}/some_more_path",
           "${workspaceFolder}/some_more_other_path"
         ]
   },
   "configurations": [
       {
           "name": "Debug",
           "includePath": [ "${default_includePath}" ],
           "defines": [
               "${default_defines}",
               "${default_defines2}",
               "_DEBUG"
           ],
           "intelliSenseMode": "msvc-x64",
           "cStandard": "c89",
           "forcedInclude": [ "${default_forcedInclude}" ],
           "browse": {
               "path": [ "${default_browsepath}" ],
               "limitSymbolsToIncludedHeaders": true
           }
       }
   ],
   "version": 4
}

Expected behavior

I did not expect it to show a warning and yellow squiggles.

Logs
Insert logs here.

Screenshots

image

Additional context

@michelleangela michelleangela added bug Feature: Configuration An issue related to configuring the extension or IntelliSense Language Service labels Apr 16, 2020
@michelleangela michelleangela added this to the 1.0.0 milestone Apr 16, 2020
@sean-mcmanus sean-mcmanus added fixed Check the Milestone for the release in which the fix is or will be available. quick fix labels Apr 17, 2020
@sean-mcmanus sean-mcmanus removed their assignment Apr 17, 2020
@sean-mcmanus
Copy link
Collaborator

@github-actions github-actions bot locked and limited conversation to collaborators Oct 8, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Feature: Configuration An issue related to configuring the extension or IntelliSense fixed Check the Milestone for the release in which the fix is or will be available. Language Service quick fix
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants