Those should be included already though in
https://github.com/geany/geany/blob/master/scripts/gtk-bundle-from-msys2.sh#L251
we still have "win32". Maybe I missed to update ir accordingly.

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

Fixed via #4088.

Admittedly, I have no clue about LSP but some how intuitively I assumed
the client and server communicate via network.
Could this be a solution, to (at least on Windows) have the plugin talk
to the server via TCP/UDP/whatever network protocol?

Some servers support TCP/IP communication but typically stdin/stdout is used (the client, i.e. the LSP plugin, is responsible for launching/terminating servers so it normally has access to their stdin/stdout).

Ok, thanks for clarification.

(I can see you haven't tried the LSP plugin yet :-P)

Yeah, sorry. I blame work and going on vacation for being distracted to play with the LSP plugin :D.

That said, I have an idea (or hope at least).

The same problem on a native x86_64 machine. I suspect the cause is the g_spawn_async_with_pipes_and_fds() call here

https://gitlab.gnome.org/GNOME/glib/-/blob/main/gio/gsubprocess.c?ref_type=heads#L402

because it uses the helper binary. If I replaced it with Geany's spawn_async_with_pipes(), it might work. But that means creating my own copy of gsubprocess.c and related files like the windows implementations of input/output streams. And worst, developing it under Windows. I probably won't do it in the short term.

Fair enough.
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.

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