hi, a bit of a wip but builds fine. I've tried it and failed running the simple example:
$waypipe ssh localhost foot S57855: 33.373875 [src/server.c:638] Env. var XDG_RUNTIME_DIR not available, cannot place display socket for WAYLAND_DISPLAY="wayland-RKaH4ZVq" i guess this has to do with sshd's PermitUserEnvironment but adding PermitUserEnvironment XDG_RUNTIME_DIR to /etc/ssh/sshd_config and restarting sshd didn't help, and $waypipe ssh localhost env XDG_RUNTIME_DIR=/tmp/run/1000 foot doesnt find the env var either. I guess i'm too stupid to figure out how env vars can be forwarded by ssh. $waypipe -d ssh localhost foot c82253: 43.101353 [src/client.c:706] I'm a client listening on '/tmp/' / 'waypipe-client-heZymjoK.sock' c82253: 43.102100 [src/client.c:707] version: 0.8.6 c82253: 43.103518 [src/client.c:752] A wayland compositor is available. Proceeding. s28697: 43.244780 [src/server.c:593] I'm a server connecting on /tmp x waypipe-server-heZymjoK.sock, running: foot s28697: 43.244974 [src/server.c:594] version: 0.8.6 S28697: 43.244995 [src/server.c:638] Env. var XDG_RUNTIME_DIR not available, cannot place display socket for WAYLAND_DISPLAY="wayland-heZymjoK" c82253: 43.252103 [src/util.c:498] Child process 33216 has died c82253: 43.252131 [src/client.c:564] Child (ssh) died, exiting from my understanding in linux-land they set XDG_RUNTIME_DIR via pam (sheesh) it _is_ working fine though with the more complex example of https://gitlab.freedesktop.org/mstoeckl/waypipe/-/tree/master#usage eg $waypipe -s /tmp/socket-local client in a term and $ssh -R /tmp/socket-remote:/tmp/socket-local -t localhost env XDG_RUNTIME_DIR=/tmp/run/1000 waypipe -s /tmp/socket-remote server -- foot in another correctly spawns a foot window in the running wayland/sway version. Landry
waypipe.tgz
Description: application/tar-gz
