Sway: SWAYSOCK not set inside xwayland

[crondog]

This means that sway --get-socketpath returns "sway socket not detected"

It is not too much of an issue but more of an inconvenience.

[ddevault]

Can you elaborate? It's set so far as I can tell.

[crondog]

So inside sway if I open termite (native wayland) and run swaymsg i get { success : true}. If i use st (xwayland) and run swaymsg I get sway no socket detected

[ddevault]

Interesting. I cannot reproduce.

[crondog]

I thought it might have been because I have xorg in tty1 but I tried just with sway and no xorg running at all and it still happens.

[crondog]

Ok I know how to reproduce.

Open sway spawn a terminal with tmux: st -e tmux
Exit sway without closing st. Just mod+shift+e
Check the processes. You should see tmux still running.
Run sway again.
Open terminal
Run swaymsg and it wont work

[ddevault]

Okay if you reattach to a tmux that was created with an older SWAYSOCK then of course it's not going to work.

[crondog]

Hmm I would have thought that tmux would have been killed when I exit sway.

[ddevault]

The entire purpose of tmux is to do the opposite.

[FreeFull]

You can set which variables tmux grabs from its environment when it's attached in a terminal using the update-environment option. By default it's set to copy over some environment variables relating to Xorg.