Killing psc-ide-server on windows naively doesn't work as only the parent process is killed, so we end up leaving the actual server up forever nwolverson/vscode-ide-purescript#3. Need to kill the entire tree: https://github.com/atom/atom/blob/v0.187.0/src/buffered-process.coffee#L166

I see you added support for --polling via kritzcreek/purescript-psc-ide@a39cb95, but looks like this defaults to false and cannot be re-configured in purescript-ide-purescript-core?

Add currentModule field to the completion request:

https://github.com/purescript/purescript/blob/master/psc-ide-server/PROTOCOL.md#complete

purescript/purescript#2946 purescript-emacs/psc-ide-emacs#109

I'm getting this error:

Found multiple psc-ide-server executables; using /usr/local/bin/psc-ide-server

But it's not clear where it's finding the "other" executable? If I npm uninstall -g purescript then it doesn't find any.

Though paths are normalised, I ended up with a case where I had C:\foo\bar fs c:\foo\bar which warned the path was wrong. Can probably just compare case insensitive and not warn otherwise.

Tried the naive thing by "purescript.pscIdeServerExe": "docker-compose run --rm purescript psc-ide-server", which is a valid command in the workspace directory, but of course the core code expects to find the executable on $PATH (the emacs PS integration seems to follow a similar pattern).

Other than wrapping docker calls in executable scripts or submitting a PR, is there a canonical way?

Random idea to suggest completions for the set of non-keyboard symbols defined in the parser?

Surely it's time to fold [almost] everything into purescript-language-server