Skip to content

Errors with new, unsaved files #384

Open
@purcell

Description

This is a question, and not necessarily an issue report.

Using elm-language-server (which mostly works great with eglot, thanks!), if I create a new file buffer Foo.elm in an eglot-managed project, I observe errors until the buffer is saved. Specifically, completion (or eldoc) requests containing the new file path are sent to the language server back end, which crashes or throws errors.

I'm not familiar enough with LSP to know whether:

a) This is an issue with the language server back end, because it should have well-defined behaviour if passed invalid file paths, or
b) eglot is sending file-related requests to the language server that are invalid because they refer to non-existent files, or
c) both of the above

I suspect that the answer is c). :-)

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions