Let me guess… You have an Nvidia card.
The latest Nvidia drivers have broken composition in Xfce, so I’ve been raw-dogging basic X11. It’s like I’m using WinXP again.
Damn using barebones X11 is crazy
Wayland is overall just better. I know there are plenty of apps that keep people on X11 just because they don’t properly support/work on Wayland yet, but other than that I’m not sure why you would want to stay on X11.
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.
Wayland is a sports car - modern, tailor made for performance. X is like a '99 Civic that’s had the seatbelts stripped out and the airbags replaced with cameras that let all the other cars on the road see you naked.
It’s fine to prefer X, but the older it gets the more people are going to roll their eyes at you. XWayland is fine for random old stuff, but there is zero reason X should be running your whole display these days.
Inb4 someone mentions network transparency that gimps the rest of the system or some 5000 year old app that needs to sniff events sent to every other program.
Plenty life in X11 yet.
Xlibre running around.
Pheonix on the horizon. (Zig!)
An anti-DEI fork by a wingnut and a project that isn’t even half way ready to use starting from scratch in a niche language. Neither of which are capable of dealing with the fundamental problem of X, the protocol itself, without becoming something entirely different.
… I’m not holding my breath.
If you deal with the fundamental problems of the protocol itself and also provide backwards compatibility… Congrats, you’ve just reinvented Wayland and XWayland.
Dealing with X11’s problems while still being X11, when X11 is the problem? Yeah, I wouldn’t hold my breath either.





