gtklock-runshell-module VS dotfiles

I may split the gtklock countdown stuff into its own module. I already built it to see if it helps with issue-2 (it doesn't). It may be a layer-shell issue as it works fine as a plain window (gtklock -li)

Here's how to do it - in this example, I'm using my sway-menu python script to generate the menu itself. I'm also moving the menu to be near the cursor:

Maybe try my script sway-runner

As a geriatric user of sway, I don't always remember the keystrokes in the more esoteric corners of my configuration. I find that my script sway-menu helps with the bulk of the uncommon key bindings. But when I drop into a 'mode' (eg "move" mode) I don't always remember all the clever things I programed into it.

I wrote a simple bash script bluetooth-timeout to power-off the linux bluetooth stack after 10m of activity. Maybe this would help you.

Another source for ideas is to read through the configs and scripts written by others. I offer my own here - there are many others around.

sway-menu

Here's a script that uses nwg-wrapper to display a countdown - it would be easy to modify it to display a digital clock.

Imma gonna browse through your stuff to see if there's a scratch to a hitherto unnoticed itch that I can snarf. You might like to do the same with my dotfiles - particularly bin/sway-\, *.config/sway** and .config/waybar.

You might be able to modify my sway-next-empty-workspace script for that. Maybe see if changing swaymsg to i3-msg does the job.

I use myclipman to wrap clipman with wayland/swaywm to prevent passwords being cached.