v3.4.0

[gnikit]

What's New (PRE RELEASE)

🎉 Modern Fortran Release of v3.3 🎉!

• Run and Debug individual files
• LFortran Linter support
• Log Channel improvements
  • Colourized Logs
  • Setting verbosity level
• Improved Installation of dependencies using VS Code Tasks
• fypp linting support
• Improved linter diagnostics
• Performance Improvements
  • Improved performance of the linter
• Update native symbol provider
• Added options
  • Hide Release Notes
• Added Fortran Logo icon

Run and Debug individual files

You can now run and debug individual files. This is useful for debugging small snippets of code. To do this, right-click on the file and select Run File or Debug File from the context menu.

LFortran Linter support

The LFortran linter is now available in the extension. It can be enabled by setting the fortran.linter.compiler setting to lfortran.

Log Channel improvements

The Modern Fortran log channel has had a small revamp.

Colourized Logs

Logs are now colorised to make reading them easier

Setting verbosity level

You can now choose the verbosity level of the extension by setting the following option in the settings

{
  "fortran.logging.level": "Error"
}

Improved Installation of dependencies using VS Code Tasks

The extension dependencies are now installed using Visual Studio Code's Tasks. That means that the commands are run from within the VS Code terminal, inheriting any environment variables already present. Particularly useful when using Python virtual environments.

fypp linting support

Adds some initial support for fypp when using gfortran. More compilers will follow soon!

Improved linter diagnostics

Add support for parsing plain text diagnostics from gfortran v11+
thus allowing the display of multiline diagnostics

module err_mod
    private
    implicit none   ! <- Error here previously not shown
    contains
        subroutine foo(arg1, arg2)
            integer, intent(in) :: arg1, arg2
            print*, 'arg1:', arg1, 'arg2:', arg2
        end subroutine foo
        subroutine proc_with_err()
            call foo()
        end subroutine proc_with_err
end module err_mod

Performance Improvements

Some additional performance improvements have been made to the extension.

Improved performance of the linter

Converted the linter into using asynchronous processes, which should improve the overall performance and responsiveness of the diagnostics.

Update native symbol provider

The native symbol provider (one used when fortls) is not present) has been updated
to use the new VS Code API.

Added options

Hide Release Notes

Hide release notes when the extension in being installed or updated.

"fortran.notifications.releaseNotes": true

Added Fortran Logo icon

Added a new icon for the Fortran Language files

Full Changelog: v3.2.0...v3.4.0

---

This discussion was created from the release v3.4.0.

[awvwgk]

Is it useful to have a discussion thread for the release here and on discourse?

[gnikit]

The audiences between the 2 are not necessarily the same, but in all honesty it was more muscle memory rather than a conscious decision to start a discussion. FYI one thing that GitHub Discussions have over the Discourse is integration with the rest of the GitHub repo, like creating issues from a discussion.

[vgovze]

I haven't seen anyone comment on discourse.

the pre-release version has problems finding the fortls binary.
The current release version (v3.2) doesn't have an issue here.
Has the configuration or anything else changed in this regard?
I have updated the fortls to 2.13.0, the problem persists.

Kind regards

[vgovze]

Thank you for the quick response. I'll let you know if everything is working after the update.

For other diagnostic info, if it is still going to be of use. I am running Windows 10 and
no, the fortls is not in my path. I have provided only the path to the binary in the VScode
settings, which seems to have worked so far now.

I hope this is what you require from the log (the output panel in VScode -> Modern Fortran).

[gnikit]

Have a try now, there is a pre-release out now. For future ease of use I added a Nightly build for the extension that runs every day Monday-Friday at 00:00 that will publish a pre-release for users to download. I think the issue should now be fixed.

[vgovze]

I've tried and it works in Pre-release version v3.4.2022100613. This issue is most probably resolved, thank you.

But in version v3.4.2022100702 of Pre-release (current), the fortls doesn't even start. I think this is a new
issue.

This is the entire output I get from the output panel from the ModernFortran extension.

After trying to restart the language server from the command palette (Fortran: Restart the language server)
this error message pops out.

A similar error message pops up when running (Fortran: What's new).

[gnikit]

You can install the previous pre-release version if your press the arrow next to the Uninstall button.
The issue that you are encountering is only on Windows on UNIX platforms I did not encounter it. It appears that the extension does not activate properly I will have a look.

[vgovze]

It is now working fine. Thank you.