From f2639226c7431bc11472ca19a4994e722d33ad22 Mon Sep 17 00:00:00 2001 From: Johan Malm Date: Tue, 9 Sep 2025 21:21:04 +0100 Subject: [PATCH] labwc-config(5): add example for autoEnableOutputs ...with inspiration from example in #3059 by @jlindgren90 --- docs/labwc-config.5.scd | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/docs/labwc-config.5.scd b/docs/labwc-config.5.scd index 95600d3b..a854d886 100644 --- a/docs/labwc-config.5.scd +++ b/docs/labwc-config.5.scd @@ -228,6 +228,23 @@ this is for compatibility with Openbox. unless an external tool such as `wlr-randr` or `kanshi` is used to manage outputs. + The reason for the existance of this option is that after losing signal + from the PC (e.g. by `wlopm -off`), some monitors do an input detection + that makes it appear (from the PC side) to disconnect and reconnect a + few seconds later, causing the monitor to turn back on again (as labwc + auto-enables newly connected outputs by default). + + An example usage pattern to avoid the above behavior looks as follows: + - Set ** to *no* + - Run kanshi (e.g. from autostart) and rely on it to enable new outputs + - Have swayidle kill and restart kanshi when entering powersave as + follows: + + ``` + swayidle -w timeout 600 \\ + 'pkill kanshi ; wlopm --off \*' resume 'kanshi & wlopm --on \*' + ``` + ** [yes|no] Try to re-use the existing output mode (resolution / refresh rate). This may prevent unnecessary screenblank delays when starting labwc