Closed
Description
Is there an existing issue for this?
- I have searched the existing issues
I have tried the Pre-Release of the extension.
- I have replicated the Issue in the latest Pre-Release
Description
When using glob/variable expansions in setting either the linter.modOutput or linter.includePaths options, the expansions can sometime result in mixed slashes in paths. While Windows itself is generally indifferent to this, it is problematic for the glob package starting with major version 8 (which only successfully resolves patterns with POSIX-like forms) and for Intel Fortran Classic (which in some cases can report files not found if paths use POSIX slashes).
Screenshots
No response
Expected Behaviour
Extension should be slash-agnostic so settings can be set to consistent values for all platforms for multi-platform projects.
Version of Modern Fortran
v3.4.2023112801
Version of Visual Studio Code
v1.85.0
Platform and Architecture
Windows
Additional Information
No response