You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Somewhat related to #1015, I found that I could not use the expansion variables, since they resulted in \ path separators in that part of the path. The include path was only properly recognized by the linting if only/ path separators were used, which isn't portable since I had to explicitly specify the full path. Is there a way around this?
It seems like this can't be configured at the VS Code level, but maybe the extension could/can?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Somewhat related to #1015, I found that I could not use the expansion variables, since they resulted in
\path separators in that part of the path. The include path was only properly recognized by the linting if only/path separators were used, which isn't portable since I had to explicitly specify the full path. Is there a way around this?It seems like this can't be configured at the VS Code level, but maybe the extension could/can?
Beta Was this translation helpful? Give feedback.
All reactions