this post was submitted on 21 Apr 2025
719 points (98.3% liked)

linuxmemes

24570 readers
2988 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
    • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
    • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
    • Β 

    Please report posts and comments that break these rules!

    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    719
    gasp (discuss.tchncs.de)
    submitted 1 day ago by Natanox@discuss.tchncs.de to c/linuxmemes@lemmy.world
    97 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] cmhe@lemmy.world 3 points 6 hours ago* (last edited 6 hours ago) (2 children)

    I also switched to use different Wayland compositors many years ago for my main systems, but there are also still reasons to use X11. These are mine:

    • X11 forwarding, with that you can connect to another system via SSH (e.g. via ssh -Y) and just start a GUI app, and the window appears on your screen.
    • Sharing individual windows via WebRTC, with Wayland compositors you can normally only share full screens. Xserver allows applications to directly capture the window content of others.
    • Easily mirroring screens for presentations, with some Wayland compositors you have to capture one screen and then play it back on another screen, with X11 that is integrated into the xserver.
    • Automation and keyboard macros, with X11 it is much easier to automate keyboard macros and customize keyboard mapping than on Wayland. See Xmodmap, etc. Same for mouse input. That is also a reason why implementing remote control software is more difficult with Wayland, see for instance RustDesk support for Wayland (works now, but still a bit experimental).

    There might be some Wayland compositors that worked around that, but on X11 this was standard. But generally X11 provides these features for all WMs, and in Wayland they have to be implemented individually.

    And some just are not supposed to work, for security reasons.

    But all of this depends on your use-case. I sometimes even (can or have to) go without a Wayland compositor or X11 and render GUI directly via KMS/DRM.

    [–] ILikeBoobies@lemmy.ca 5 points 6 hours ago* (last edited 6 hours ago) (1 children)

    Multi-cursor support/multi focus

    If I want two mice and monitors hooked up so me and another person can use the same computer independently it’s x11

    I’ve seen some steps towards this on Wayland but it was in infancy last I checked

    [–] cmhe@lemmy.world 1 points 6 hours ago (2 children)

    I think you can start two Wayland compositors, and change the compositor configuration to use different mice and outputs, but I never tried this.

    [–] ILikeBoobies@lemmy.ca 1 points 1 hour ago

    Thanks for the tip

    [–] highball@lemmy.world 1 points 4 hours ago

    I'd wager that is true. I know, for sure, you can start one compositor inside another compositor. I do this all the time for gaming with gamescope.

    [–] glowing_hans@sopuli.xyz 1 points 6 hours ago (1 children)

    Automation and keyboard macros,

    Isn't there xdotool for this?

    [–] cmhe@lemmy.world 1 points 6 hours ago* (last edited 6 hours ago) (1 children)

    Yes, that is for X11. Now find one that works on all Wayland compositors, that doesn't require root permissions.

    [–] glowing_hans@sopuli.xyz 3 points 6 hours ago (1 children)

    I guess wtype is waylands replacement for xdotool? https://github.com/atx/wtype

    [–] cmhe@lemmy.world 2 points 6 hours ago

    Pretty good, however wtype is only sending keystrokes globally, with xdotool you can also move the mouse, send key events to specific windows and more.