Wez Furlong d7145561c2 Add wezterm start --domain DOMAIN --attach + gui-attached event ... The motivation here was to remove some similar but not quite the same logic that existed for starting up when using `wezterm connect`. Now `wezterm connect DOMAIN` is implemented as `wezterm start --domain DOMAIN --attach --always-new-process` and a little extra hand-wave to ensure that the default domain is set correctly. The startup events have been refactored a bit; a new gui-attached event is emitted after attaching and starting any default programs in the selected domain at startup. That event can be used to maximize windows and so on, if desired. The gui-attached event is independent of the startup command and fires for `wezterm connect`, which `gui-startup` did not (and could not) do.		2023-01-26 15:56:11 -07:00
..
gui-attached.md	Add wezterm start --domain DOMAIN --attach + gui-attached event	2023-01-26 15:56:11 -07:00
gui-startup.md	Add wezterm start --domain DOMAIN --attach + gui-attached event	2023-01-26 15:56:11 -07:00