Continued absurd Linux problems:
If I run in Wayland,
and run Chrome,
my custom .XCompose file is ignored.
Chrome on X11 does not have this problem,
Wayland apps other than Chrome do not have a problem,
if I use default XCompose sequences instead of custom XCompose there is no problem.
It's just this one combination of things.
Checking the Chromium bug tracker I find variations of this bug repeatedly filed, then closed, as far back as 2015 and as recently as 2021, closed as "fixed".
So I'm sitting here trying to figure out how to tell if a particular app is running in Wayland or XWayland.
This is the answer I get off Stack Overflow. I'm thinking… No. No, that's too silly. It can't be the best way.
I keep researching. It's the best way.
You run xeyes.
Wayland has security that keeps windows from knowing about mouse events in other windows. XWayland doesn't.
Xeyes will track your cursor whenever you're over an XWayland window, then stop if you pass over anything else.
> Such a feature would have to be implemented at the window manager level of wayland instead
the unix philosophy of "do one thing and do it well" and "write programs to interop with each other" is screaming in the corner
every wayland decision just seems like it was made by the same folks who asked "Why do you think a volume control is necessary?" when making a audio player
i still find it funny that macOS -- the OS that markets itsself on security & privacy still lets you do more than Wayland on Linux, the place that people see as infinately customisable
like i like win32 bc it lets you do wacky shit easily (much less important than a11y but i want my blastbtn god damnit), why would i want my desktop computer to act like a phone where apps don't even know if they're in the foreground
mcc
Morgan Gangwere
Chartreuse
taylor 