Replies: 1 comment 3 replies
-
it's really hard to say because there's not a lot of wezterm specific information included here, no error messages to interpret, and I'm not familiar with toolbox. In theory, you should be able to use a config.unix_domains = {
{
name = "something",
proxy_command = {"toolbox", "run", "--container", "something", "wezterm", "cli", "proxy" },
}
} If proxy_command = {"toolbox", "run", "--container", "something", "env", "XDG_RUNTIME_DIR=/something", "wezterm", "cli", "proxy" }, |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What Operating System(s) are you running on?
Linux Wayland
Which Wayland compositor or X11 Window manager(s) are you using?
Mutter (GNOME 46, Fedora Linux 40.20240429.0 (Silverblue))
WezTerm version
20240203-110809-5046fc22 (Flatpak)
Ask your question!
I'm trying to better integrate WezTerm and my (admittedly odd) workflow that's based on
toolbox
/toolbx
.What I would like to do is create a unix domain where the mux-server is spawned inside a
toolbox
. The issue I'm running into is that I can't see how to change the socket path for a domain while having a single config. Because/run/user
and$HOME
are shared across all the sandboxes, the various domains need separate sockets. I've tried:wezterm.gui
or notwezterm-mux-server
directlyThese all result in the same socket path being used.
Am I being insufficiently clever with my config or is this not possible?
Beta Was this translation helpful? Give feedback.
All reactions