dotfiles VS cage

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.

You... might be able to, kind of, depending on your goal... So the thing is, if all you need is a single screen (or at least, I've not run this multi-monitor) and you're just working around drivers that don't support Xorg, you can just run cage ( https://github.com/cage-kiosk/cage ), run xwayland on that, and run your real GUI on that. Of course, then you're skipping all the advantages of wayland except hardware/driver compatibility.

For "real" wayland, sibling comments are correct that you'd need a wayland compositor that reimplemented awesome.

> As a developer, I needed to port a custom Linux system to hardware that only has Wayland drivers and it was a giant pain. Wayland offers no advantage at all for that system but it broke a lot of functionality that relied on X in terms of window placement, etc.

FWIW, I've had decent luck running cage ( https://www.hjdskes.nl/projects/cage/ ), then on that xwayland, and then just ignoring wayland and running X clients. The result does still have some slight quirks, but it mostly works fine.

That did help me find https://github.com/cage-kiosk/cage/wiki initially I'm here there's other going down that path. Thanks

I thought this was going to be some development news with Wayland compositing going further: https://emacsconf.org/2022/talks/wayland/. Maybe it's because 29.1 was on my mind with the full Wayland client support being released.

If you want to just run one application in a modern way (yes, I'm assuming you agree that Wayland is desirable), then check out https://www.hjdskes.nl/projects/cage/.

You can run Wayland inside Xorg via cage[1] so you don't need to use a Wayland compositor.

[1]: https://github.com/cage-kiosk/cage

Just ran into cage, seems useful.

It's kiosk mode. Sometimes related to POS. You can use https://github.com/cage-kiosk/cage (Wayland) for example.

Maybe starting with reimplementing something like this: https://github.com/cage-kiosk/cage would be the easiest?