diff options
| author | Sean Whitton <spwhitton@spwhitton.name> | 2023-06-05 10:33:36 +0100 |
|---|---|---|
| committer | Sean Whitton <spwhitton@spwhitton.name> | 2023-06-05 10:33:36 +0100 |
| commit | 08e2062c996e7cd0fe58ae05c7cb0a7b579eaab1 (patch) | |
| tree | 0590a1ff7e8b93acce196f76018cabdd455c5d1f /.config | |
| parent | 9a532695a882101359d216d52515871105483ad3 (diff) | |
| download | dotfiles-08e2062c996e7cd0fe58ae05c7cb0a7b579eaab1.tar.gz | |
move swayidle config out to its own file
Diffstat (limited to '.config')
| -rw-r--r-- | .config/sway/config | 11 | ||||
| -rw-r--r-- | .config/swayidle/config | 10 |
2 files changed, 11 insertions, 10 deletions
diff --git a/.config/sway/config b/.config/sway/config index 981e01d5..a8cc27bd 100644 --- a/.config/sway/config +++ b/.config/sway/config @@ -374,6 +374,7 @@ input type:keyboard repeat_delay 380 seat * hide_cursor 5000 exec mako +exec swayidle -w exec emacsclient --spw/update-environment exec emacsclient -sgdbmacs --spw/no-start --spw/update-environment @@ -381,14 +382,4 @@ exec_always fcitx5 -d --replace output * bg ~/src/dotfiles/lib-src/img/green_gobbler.png tile -# Ideally we wouldn't try to call swaylock if the screen is already locked, -# but discovering whether swaylock is already running in a way that avoids -# races is difficult or impossible because swaylock doesn't have a mechanism -# to report that it's successfully locked the screen other than daemonising. -# So, until it does, the following means a lot of "failed to lock; already -# locked?" messages on stderr. -exec swayidle -w \ - lock 'swaylock -f' before-sleep 'swaylock -f' timeout 300 'swaylock -f' \ - timeout 300 'swaymsg "output * dpms off"' resume 'swaymsg "output * dpms on"' - include ~/.config/sway/$(hostname)/* diff --git a/.config/swayidle/config b/.config/swayidle/config new file mode 100644 index 00000000..5176407a --- /dev/null +++ b/.config/swayidle/config @@ -0,0 +1,10 @@ +# Ideally we wouldn't try to call swaylock if the screen is already locked, +# but discovering whether swaylock is already running in a way that avoids +# races is difficult or impossible because swaylock doesn't have a mechanism +# to report that it's successfully locked the screen other than daemonising. +# So, until it does, the following means a lot of "failed to lock; already +# locked?" messages on stderr. +lock 'swaylock -f' +before-sleep 'swaylock -f' +timeout 300 'swaylock -f' +timeout 300 'swaymsg "output * dpms off"' resume 'swaymsg "output * dpms on"' |