Linux

15495 readers

407 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 3 years ago

MODERATORS

Ategon@programming.dev

anzo@programming.dev

dwraf_of_ignorance@programming.dev

What are some things X11 can do that Wayland still can't? (piefed.zip)

submitted 2 days ago by mrbigmouth502@piefed.zip to c/linux@programming.dev

94 comments fedilink hide all child comments

The biggest thing I can think of is that X11 is more flexible when it comes to specifying custom resolutions; which some people use to output 240p on CRT TVs for emulation. AFAIK, there is currently no real equivalent for xrandr on any Wayland compositor.

I've also noticed that Grsync's password prompt is broken on Wayland. Thankfully, it has a feature that lets you preview the command it's about to run, so that you can copy and paste it into a terminal.

Being a KDE user on EndeavourOS, I use Wayland everyday. I switched over a few years ago for Waydroid, but now X11 isn't even an option for me with the current release of KDE.

you are viewing a single comment's thread
view the rest of the comments

[–] TwilightKiddy@scribe.disroot.org 27 points 2 days ago* (last edited 2 days ago) (2 children)

It's not about creating global hotkeys, it's about registering them from a running program. There is nothing preventing you from creating a compositor-level keybinding, but an app cannot do that unless it figures out what compositor you are running and then handles the configuration for each and every compositor in existence.

[–] 2ndDegreeOWO@lemmy.world 7 points 2 days ago

Ah, okay then. Might be worth a try.

[–] mrbigmouth502@piefed.zip 3 points 2 days ago (1 children)

I wouldn't worry about supporting every compositor in existence. Ideally, the Wayland spec would be unified, but it's not.

I feel like if someone created a compositor with an extension for that feature, it'd eventually become popular enough that people would start implementing that extension in other compositors.

[–] TwilightKiddy@scribe.disroot.org 7 points 2 days ago (1 children)

I wouldn't want that. I'm fairly content with the fact that no random apps can grab my keystrokes unless that specific app is focused. From what I heard, for most people the only global keybind they want is muting their microphone. You can implement that yourself with absolutely no trouble, it will usually be the first example in the global keybinds configuration docs for pretty much any compositor. People who don't want to deal with writing configs can use KDE where you have a GUI to configure the same thing.

[–] mrbigmouth502@piefed.zip 1 points 1 day ago

Like I said in a different comment, if such a feature exists, it should be an opt-in thing. It shouldn't be something that's enabled by default. Heck, I think you could use a permissions-based model where you could specify which apps can read your keystrokes, and which can't.