Skip to content

bug: internal vscode module output #698

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.

Sign up for GitHub

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

Jump to bottom
Closed
1 task done
gnikit opened this issue Oct 6, 2022 · 0 comments · Fixed by #699
Closed
1 task done

bug: internal vscode module output #698

gnikit opened this issue Oct 6, 2022 · 0 comments · Fixed by #699
Assignees
@gnikit
Labels
bug

Comments

@gnikit
Copy link
Member

gnikit commented Oct 6, 2022

Is there an existing issue for this?

  • I have searched the existing issues

Description

The default directory for persistent caching in vscode in the absence of a modOutputDir does not always exist. We should make sure the directory is created before we start outputting module files in it.

Screenshots

No response

Expected Behaviour

Create directory upon initialisation

Version of Modern Fortran

v3.4.2022100613

Version of Visual Studio Code

1.72.0-insider

Platform and Architecture

Linux

Additional Information

Version: 1.72.0-insider
Commit: 64bbfbf67ada9953918d72e1df2f4d8e537d340e
Date: 2022-10-04T23:18:45.080Z
Electron: 19.0.17
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Linux x64 5.15.0-48-generic
Sandboxed: Yes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gnikit gnikit

Labels
bug
Projects
Modern Fortran Release v4.0.0
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

bug: internal vscode module output fortran-lang/vscode-fortran-support
1 participant
@gnikit