elcord: attempting reconnect on WSL2

[overanalytcl]

I am on Windows 11, WSL 2 on Ubuntu 24.04 and Emacs 29.4. I installed elcord on Spacemacs, and yet when I activate elcord-mode, it hangs on elcord: attempting reconnect... This is distinct from both #48 and #70, since I am on WSL (it works perfectly fine on the native build), and as such I don't think the Powershell thing applies to me. Do you have any idea where I can start debugging this?

[Mstrodl]

If you're running emacs in WSL, you'll need to be running Discord in WSL as well. I don't think there's any real way around that.

[Mstrodl]

(On windows, discord uses named pipes, which afaik aren't exported to WSL at all)

[overanalytcl]

(On windows, discord uses named pipes, which afaik aren't exported to WSL at all)

Well, that sucks to hear. I thought RPC would flow from WSL to Discord because it shouldn't be blocked by anything (iirc, there's no firewall). Maybe an intermediate script that could function like stdpipes.ps1 that gets run on the host (so it could have access to WSL2) could work?

[Mstrodl]

Maybe! There might be some clever driver or something that lets you do named pipes directly from WSL? Happy to accept a PR to add support for it!

[RangHo]

I used to experiment with npiperelay back in the days I used WSL1. It was for NeoVim, though...

With this solution, you use npiperelay with socat to create a "Discord IPC UNIX socket" yourself. Basically how it works is:

• You create /tmp/discord-ipc-0 or whatever as a UNIX socket to trick Elcord, and...
• ...create npiperelay instance with Discord IPC named pipe on Windows side, and...
• ...let socat bridge these two so that Elcord's request are tunneled to the Windows named pipe.

Here is a one-liner, adapted from some sample commands (untested, since I ditched Windows years ago):

socat UNIX-LISTEN:/tmp/discord-ipc-0,fork EXEC:"npiperelay.exe -ep -s //./pipe/discord-ipc-0",nofork