Use default clipboard provider for wezterm connect

[alvin883]

In wezterm, they had their own method (wezterm connect) to run wezterm daemon on the remote that uses ssh as a channel

reference: https://wezfurlong.org/wezterm/multiplexing.html#ssh-domains

Because of that, default env such as WAYLAND_DISPLAY & DISPLAY is still exist, so when we run helix through wezterm connect and yank selections to clipboard (<space>y) it doesn't do anything (somehow in my case helix will just hang? idk why)

Therefore we need to check for WEZTERM_UNIX_SOCKET before anything else, and just use fallback provider for that, so we can copy to clipboard even with wezterm connect 🎉

Thanks!

[pascalkuthe]

how would this interact with tmux users on wezterm? I think they would still want to use the tmux provider?

[alvin883]

@pascalkuthe I never use tmux in wezterm because that's suppose to be a replacement, but since you mentioned it, now I updated to code to prioritize tmux provider if it's used inside wezterm connect

Before

I've tested with current master, apparently copy to clipboard is not working for both wezterm & tmux inside wezterm connect, because it's detected wayland env

wezterm connect

tmux in wezterm connect

After

wezterm connect

tmux inside wezterm connect

Thank you!