Simon Ser

I wonder if "grouped" is the right terminology here? The i3 user guide only uses the terms "tabbed layout", "stacking layout" and "split layout".

Seems like this is missing some files?

Hm, not sure I'm following. Why not grab the toplevel list via the Wayland protocol rather than the Sway IPC? That way it's not specific to Sway?

For the first use-caae there is e.g. https://git.sr.ht/~leon_plickat/lswt For the second use-case that sounds like a good idea but note that with this method users won't be able to select...

There's no spec for SVG cursors yet. KDE just merged experimental support for these a few days ago. I do agree that SVG cursors would be better, and I'm following...

I think this would be a nice feature. I've dropped my thoughts in https://github.com/Ferdi265/wl-restart/issues/2#issuecomment-2419679363, and pinged KDE folks about it.

For reference, how does i3 behave here?

I don't see a reason why it wouldn't work. The `--to-code` option makes it so Sway sticks to a specific physical key regardless of the keyboard layout.

Not sure what you mean… What is the behavior you see, and what is the behavior you'd expect?

It should use PATH. You can also set `swaybar_command`.