No, gspawn-win64-helper.exe and gspawn-win64-helper-console.exe seem to be missing from the script.

Fixed via #4088.

Possibly not needed at all because these probably cause the extra console window with the server and if I manage to get it running with the Geany's spawn module, they won't be necessary either.

Yeah but probably won't cause harm and might help if plugins or any code uses g_spawn_* API.

Windows is so much a hassle, at least with Geany's tech stack and probably not worth the efforts to get the LSP integration running. Or someone actually using it need to provide the necessary code changes.

I wanted to give it a try and followed https://wiki.geany.org/howtos/win32/msys2 to build geany and geany-plugins which I managed to do.
However, when I start Geany using /c/geany/bin/geany.exe, no plugins are loaded (even not those bundled with geany itself). I also tried to set "extra plugin path" within Geany to the directory containing them but that didn't help. Any hints?

I assume the g_win32_get_package_installation_directory_of_module() might not work. Maybe the "System data dir" (as reported in Help->Debug Messages) is wrong.

I usually start Geany from "c:\program files\geany" directly in Windows, not from the MSYS2 shell.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.