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
Added 3 commands for:
- Running the initialisation process for the linter
- Cleaning the linter produced files e.g. .mod
- Cleaning all diagnostics produced by the linter
Added the settings to:
- Run the initialisation of the linter upon extension activation
- Added the experimental setting of discarding the full project-wide diagnostics produced
by the initialisation process
Edited the descriptions of 2 existing settings
Added additional extension activation events on commands
"markdownDescription": "Compiler used for linting support.",
232
240
"order": 0
233
241
},
242
+
"fortran.linter.initialize": {
243
+
"type": "boolean",
244
+
"default": true,
245
+
"markdownDescription": "Attempt to initialize the linter by mock-compiling all files in the workspace.",
246
+
"order": 5
247
+
},
234
248
"fortran.linter.compilerPath": {
235
249
"type": "string",
236
250
"default": "",
@@ -257,7 +271,7 @@
257
271
"fortran.linter.modOutput": {
258
272
"type": "string",
259
273
"default": "",
260
-
"markdownDescription": "Global output directory for .mod files generated due to linting `-J<linter.modOutput>`. Can resolve internal variables with `~`, `${workspaceFolder}`, `${env}`, `${config}`, `${file}`, `${fileDirname}`, `${fileBasenameNoExtension}`.",
274
+
"markdownDescription": "Output directory for .mod files generated due to linting `-J<linter.modOutput>`. By default this is an internal VS Code path unique to each workspace. Can resolve internal variables with `~`, `${workspaceFolder}`, `${env}`, `${config}`, `${file}`, `${fileDirname}`, `${fileBasenameNoExtension}`.",
261
275
"order": 40
262
276
},
263
277
"fortran.linter.fypp.enabled": {
@@ -307,7 +321,7 @@
307
321
"std",
308
322
"gfortran5"
309
323
],
310
-
"markdownDescription": "ine numbering marker format, currently std`, `cpp` and `gfortran5` are supported, where `std` emits `#line` pragmas similar to standard tools, 'cpp' produces line directives as emitted by GNU cpp, and `gfortran5` cpp line directives with a workaround for a bug introduced in GFortran 5. Default: `cpp`.",
324
+
"markdownDescription": "Line numbering marker format, currently std`, `cpp` and `gfortran5` are supported, where `std` emits `#line` pragmas similar to standard tools, 'cpp' produces line directives as emitted by GNU cpp, and `gfortran5` cpp line directives with a workaround for a bug introduced in GFortran 5. Default: `cpp`.",
311
325
"order": 120
312
326
},
313
327
"fortran.linter.fypp.extraArgs": {
@@ -526,6 +540,19 @@
526
540
}
527
541
}
528
542
},
543
+
{
544
+
"id": "experimental",
545
+
"title": "Experimental",
546
+
"order": 500,
547
+
"properties": {
548
+
"fortran.experimental.keepInitDiagnostics": {
549
+
"type": "boolean",
550
+
"default": true,
551
+
"markdownDescription": "Keep (and show) all diagnostics generated from the initialization of the Linter, not just from opened files.",
0 commit comments