I'd recommend starting with fixing that instead. It would be much more helpful for the community.
I'd recommend starting with fixing that instead. It would be much more helpful for the community.
fwiw, we know of this limitation and decided the acceptable workaround for Windows devs is simply to host the language server and they can connect to it via TCP.
It seems that the only problem for fixing the problem is:
> Thanks for the offer, but the problem is our team being time limited / having an engineer with a Windows machine ready to take this on, not that we wouldn't want to pay someone to work on it :)
(https://github.com/pganalyze/libpg_query/issues/44#issuecomm...)
Hosting the LSP elsewhere is not really needed since if people wanted to go that way they could use Remote ssh (https://code.visualstudio.com/docs/remote/ssh) to host the whole dev environment on linux and connect to it.
Thank you
(Speaking as someone who dreaded the “inevitable” victory of Windows on the desktop in the 90s I might be a little biased/overjoyed.)
> the only problem for fixing the problem is
Hopefully it’s as easy as you make it sound!
;)
Postgres itself supports Windows, the main challenge is identifying the relevant files to pull in (since we use a subset of the full source code), and testing the changes. It should be fairly quick for someone who has C development experience on Windows, with a working development environment.