Skip to content

Utilize separate language server extension en lieu of internal support #105

Closed
@hansec

Description

@hansec

Hey, I am developing the Fortran Language Server and a companion extension for VSCode. I just updated the VSCode extension (v0.2.5) to work properly with this extension.

As there are settings that are unique to the language server I think it is best to keep this functionality in a separate extension at least for now. Once things stabilize with the language server interface it might make sense to merge the language server support into a single extension. For now though, I wanted to suggest you remove that option from your extension and point people to the language server extension. That way it is clear what settings effect which functionality and where people should report bugs.

I also wanted to say thanks! I am so glad there is actively maintained Fortran support for VSCode. So many of the Fortran editor packages I have dealt with in the past get abandoned without updates for new syntax and bug fixes.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions