Wez Furlong fb50014ed5 mux: avoid inheriting wrong pane/socket env ... The first problem in #1222 is that the environment in the spawned mux server has inherited the unix socket path from the GUI that is the client, rather than the mux server. That means that `wezterm cli` is operating on the mux namespace of the client (which is a layered/wrapped view of the mux server), rather than the mux server. This fixes `wezterm cli split-pane` in the case where unix domains are in use together with `connect_automatically = true`, although there is still a really weird issue with tabs that needs to be run down. refs: https://github.com/wez/wezterm/issues/1225 (sort of) refs: https://github.com/wez/wezterm/issues/1222		2021-10-17 09:44:23 -07:00
..
src	mux: avoid inheriting wrong pane/socket env	2021-10-17 09:44:23 -07:00
Cargo.toml	Raise minimum Rust version to 1.51, de-vendor openssl on unix	2021-03-25 09:43:50 -07:00