From ff7d979d99ddb087a02fc457953b33e3beb4715b Mon Sep 17 00:00:00 2001 From: Brian Ashworth Date: Thu, 15 Aug 2019 03:00:14 -0400 Subject: cmd_xwayland: add force for immediate launch This just adds a force option to cmd_xwayland that allows for xwayland to be immediately launched instead of lazily launched. This is useful for slower machines so it can be part of the startup time instead of when the user is actively trying to use it --- sway/sway.5.scd | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) (limited to 'sway/sway.5.scd') diff --git a/sway/sway.5.scd b/sway/sway.5.scd index 8049836b..128663cd 100644 --- a/sway/sway.5.scd +++ b/sway/sway.5.scd @@ -85,9 +85,12 @@ The following commands may only be used in the configuration file. It can be disabled by setting the command to a single dash: _swaynag\_command -_ -*xwayland* enable|disable +*xwayland* enable|disable|force Enables or disables Xwayland support, which allows X11 applications to be - used. + used. _enable_ will lazily load Xwayland so Xwayland will not be launched + until the first client attempts to connect. In some cases, such as slower + machines, it may be desirable to have Xwayland started immediately by + using _force_ instead of _enable_. The following commands cannot be used directly in the configuration file. They are expected to be used with *bindsym* or at runtime through *swaymsg*(1). -- cgit v1.2.3-54-g00ecf