Looks like a hotkey daemon. That helps, but the crux of my issue is that on X11, xdotool can read the window names, size, position, and move them between workspaces and monitors.
you cannot use it via bash you configure it and it applies actions to windows as they are created you cannot use it at all where plasma isn’t your desktop and as of wayland you cannot use a different window maanager with KDE plasma as wayland doesn’t have the idea of window managers.
I don’t think you are ever again going to have an agnostic way to do this
I use bash extensively. I poll video files with ffprobe to get the audio level and video resolution to set a universal standard volume and custom window positions per file depending on what other applications are open.
I understand that all this is a security risk / too obscure of a feature from Wayland’s perspective. I’ll probably stick to X11 for as long as possible.
Window manager automation. I use hotkeys to resize and move windows based on their title, pin them to certain monitors, etc…
ydotoolis a step in the right direction, but AFAIK it can only simulate mouse and keyboard inputAre you looking for something like swhkd maybe?
Looks like a hotkey daemon. That helps, but the crux of my issue is that on X11, xdotool can read the window names, size, position, and move them between workspaces and monitors.
Windows rules on KDE?
Are KDE’s window rules accessible through bash? Can it work on individual window titles (i.e. different browser tabs in Firefox)?
Speaking as an Xfce user, I’d prefer a DE-neutral option, but if I must use Wayland, maybe KDE is worth another try.
you cannot use it via bash you configure it and it applies actions to windows as they are created you cannot use it at all where plasma isn’t your desktop and as of wayland you cannot use a different window maanager with KDE plasma as wayland doesn’t have the idea of window managers.
I don’t think you are ever again going to have an agnostic way to do this
I use bash extensively. I poll video files with ffprobe to get the audio level and video resolution to set a universal standard volume and custom window positions per file depending on what other applications are open.
I understand that all this is a security risk / too obscure of a feature from Wayland’s perspective. I’ll probably stick to X11 for as long as possible.
I meant there is no particular reason to expect a gui configuration tool for a gui Window manager that isn’t expected to be dynamic to have a cli.
Generally the use case is always maximize this window or always put it on a particular workspace etc.
If it has any path to being addressable via bash you would check its dbus interface if any.
The same feature on say i3wm also isn’t a CLI nor is it any more dynamic.
Windows rules and wmctrl don’t have identical use cases although there could be overlap