Nicholas Wolverson

Possibly URI normalisation issue, I see `file:///c%3A/Git` vs `"file:///C:/Git`. I suspect this is an issue in the language server (at least that is where the failed matching is taking place),...

Some warnings *are* being fixed though?

I think most of the above warnings should be fixable, with the exception of * Existing import, merge import lists * Duplicates in export list I'd suggest touching source files/clearing...

Seems like a candidate for a code lens (no pun intended). Source selection/running commands is something that requires client-side support so for refactoring/codegen type actions something that can be provided...

In general - at a glance it looks like purescript-tidy-codgen-lens is using the CST parser, which should integrate well here, the parsed input should already be available in the state...

This seems like a vim issue as far as I can see, I cannot help with that. I don't see any reason this should be to do with formatting specifically,...

You know it would be more useful if that error message specified what the expected path was - I assume that either this is wrong, or there is some path...

There's some oddness in the logging, but it seems that the expected root path is blank (where it says with cwd, there should be a path). I think this is...

On connection, VS Code immediately sends `didChangeConfiguration` https://microsoft.github.io/language-server-protocol/specifications/specification-current/#workspace_didChangeConfiguration At the time of someone first trying this with a non-vscode LSP client, I added the option to instead pass a JSON...

I've just published a version which supports the newer `workspace/configuration` message, as well as the existing client-push and command line config schemes, I believe there may be updated logging that...