I don't like the Linux clipboard situation

Submitted ⁨⁨3⁩ ⁨days⁩ ago⁩ by ⁨PhilipTheBucket@ponder.cat⁩ to ⁨rant@lemmy.sdf.org⁩

I cannot believe that in this the year of our lord 2025 we still have two separate clipboard buffers on desktop Linux.

There are very few cases where I will execute a paste (whether it is with middle click or Ctrl-V) and I will want the resulting paste to be anything other than the last thing I copied. Whatever X11 subcommittee came up with the idea that users would want to juggle stuff between the two buffers, or whatever the fuck the thinking was, needs to be punished physically. It’s not enough to tell them: They need to remember, so that they will know what they did was wrong, and get fearful in the future if they ever think of doing anything like that again. Their names should be made public, so that people in the future who might want to hire them will know what they did. (I tried to find out who it was, but Google is drunk again and couldn’t really tell me all that much.)

I am already aware that the X11 people spent a lot of time huffing glue in between creating overly complicated standards documents. So maybe the fact that they made some baffling and wrong decisions for literally no reason isn’t surprising. It was a long time ago, a lot of bad things happened back then. What I really cannot understand is why Wayland looked at that decision, and the long history of pain and suffering it had caused over the years, and decided, “You know what? Let’s keep that around. What harm could it do? And anyway… it’s compatible!”

Having two clipboards is literally just worse. They did extra work, and enforced extra work on every programmer and every user, just to make things worse. If anyone knows of something I can run that will just do a simple bidirectional sync between the two clipboards, so I can just pretend to myself that all of this isn’t happening, please tell me. I tried to find a solution for half the morning so far, because I finally just got enraged by it, and I couldn’t find one.

If I imagine hard to myself, I can maybe imagine a scenario where I might want to hit Ctrl-C, then I would accidentally highlight something right after, and then I would want to paste the thing I did Ctrl-C for. But surely that use case isn’t the one that we need to wrap the whole desktop Linux clipboard situation around, to make sure that Fat-Finger Freddy can still get his pasting done, all while the rest of us have to go around saying things like “wl-paste -p -w ‘wl-copy’” and everyone has to do a bunch of extra work whenever they want to do the already difficult task of making pasting work in an editor over SSH or something.

I literally can’t believe how bad it is. It’s like a prank. It’s like one of those imaginary programming languages where someone invented a deliberately malicious feature and then implemented it to a T to be funny.

I do not like it. Not one bit.

Also: Did you know there’s a secondary selection? There are actually three clipboards. Emacs is only editor in history that does anything with the third one. Hold down “alt” and drag with the left button to highlight something, and it’ll go into the top secret secondary clipboard, where nothing else will ever see it.

OH HOW USEFUL

SAID NO ONE EVER

source

Comments

Sort:hotnew top

PhilipTheBucket@ponder.cat ⁨3⁩ ⁨days⁩ ago
Okay, if anyone is curious: I finally lost so much patience with all of this that I fought with it until it was actually doing what I want. It took far longer than it should have.

Here was the secret sauce, for my setup at least:

Wayland needs running in the background:

wl-paste -w sh -c 'wl-copy -p'

So what that does is send anything from CLIPBOARD to PRIMARY, so I can click “copy to clipboard” on a web page and still middle-click to paste it. I actually don’t care as much about the other way (which is good because it seems like it might cause an infinite loop); @Riskable@programming.dev you can rest easy that the Ctrl-V buffer won’t be affected by highlighting text and I can still do paste of whatever I wanted to, even if I highlighted in the middle.

Then in Helix config on any remote machine, have:

[editor] clipboard-provider = "termcode"

That’s what enables us to highlight text in Helix and have it make it back to the local system’s clipboard. I actually don’t know which clipboard it’s going into there, and thanks to wl-paste, I don’t have to care.

Then, in kitty config on the local system, have:

mouse_map middle press ungrabbed paste_from_selection mouse_map middle press grabbed paste_from_selection mouse_map middle release ungrabbed discard_event mouse_map middle release grabbed discard_event

That means that we disable all efforts which Helix will make to grab the middle-click event and fuck it up in some way or other. Kitty pastes the text, Helix receives it, and we have the nice side benefit that it goes in where the cursor is instead of at whatever random position I have let the pointer wander over to before I did the middle click.

Hallelujah. I can get back to actual work. Boy this wasn’t a big extensive confusing waste of time involving extra difficulty that didn’t need to be there. Great. Great.
source
bjoern_tantau@swg-empire.de ⁨3⁩ ⁨days⁩ ago
😁 You’re just too late to Wayland. That’s all. Wayland’s lack of primary selection support actually kept me away for years. I like having two clipboards. One with longer lived content and one for immediate use.

Though I’ve now been disabled for quite a while and don’t use a mouse anymore. So I can’t see if there are any bugs.

I recall reading some of the debates on how to specify the support in Wayland and I remember someone bringing up the possibility of having an unlimited number of clipboard and making it the compositor/clipboard manager’s responsibility of juggling that. No idea what became of that.

source
- bjoern_tantau@swg-empire.de ⁨3⁩ ⁨days⁩ ago
  And actually, if you count dragging and dropping, there are four clipboards.
  
  source
- PhilipTheBucket@ponder.cat ⁨3⁩ ⁨days⁩ ago
  What’s the logic behind it being better to have multiple clipboards, as opposed to having a single clipboard with accessible history?
  
  I can kind of get how you might want to paste something from a longer-lived conceptual activity even if you highlighted something since then… but if you’re going to do the UI and API work to support multiple sources for the paste, why on earth should it be an arbitrary toolkit-driven decision, with no history, instead of a deliberate decision about which historical copy the user wants to paste out of all the recent copies? What advantage is gained by segregating into separate “clipboards” when we know that the great majority of apps are going to just pick one that’s their favorite and interact with only that one?
  
  source
notabot@lemm.ee ⁨3⁩ ⁨days⁩ ago
I’m very happy having the selection and primary clipboards be separate (I’ll admit I don’t use the secondary clipboard). Being able to copy one block, then select a second block, paste that in from selection and then paste from clipboard makes a lot of CLI tasks quicker.

There probably should be a setting that says ‘K.I.S.S just one clipboard please’ though, for those that prefer that way of working.

source
- PhilipTheBucket@ponder.cat ⁨3⁩ ⁨days⁩ ago
  Being able to copy one block, then select a second block, paste that in from selection and then paste from clipboard makes a lot of CLI tasks quicker.
  
  Which CLI are you using that’s hip to both the middle-click paste and the clipboard paste? What’s an example of a case where being able to hold two things in the buffer at once for pasting them both one after another makes things easier?
  
  It’s not that I don’t believe you, I’m just literally having trouble wrapping my head around how this even happens. I mean, sure, I guess. My issue is I guess much more that there are a lot of tools that only deal with one clipboard or the other, and situations where it is impossible to copy and paste from one thing to another (or was until today) just because of which toolkit one or the other thing is choosing to use. If it was two clipboards that were well-supported from everywhere, and I could always just click “copy to clipboard” in the browser and go to terminal and hit Cmd-V or something to paste it, I wouldn’t be so irritable about it.
  
  source
  - notabot@lemm.ee ⁨2⁩ ⁨days⁩ ago
    I’m still using X11, so this might be different in wayland, but in just about everything shift-insert pastes the selection and ctrl-v pastes the clipboard. In terminals paste from clipboard is ctrl-shift-v as ctrl-v already had a purpose.
    
    Copying to selection just involves highlighting the text, copying to clipboard is ctrl-c or ctrl-shift-c in a terminal.
    
    I had to actually think about those as they’re basically just muscle memory now! I might use the clipboard to store a path I need to use in multiple places, maybe in multiple tools, and the selection for ephemeral data like a snippet of output from the last command, or an ID value from a web page, something like that. It’s a bit tricky to explain, it’s just the way it’s always worked on unix and linux UIs, and it just becomes second nature to think with those tools.
    
    source
    -> View More Comments
riskable@programming.dev ⁨3⁩ ⁨days⁩ ago
Just use KDE and you get klipper which is an amazing clipboard manager. It keeps track of everything you’ve copied to your clipboard (raise the history to 999).

Configure it to pop up at the cursor location and whenever you type the keystroke you’ll have access to everything.

I personally prefer that it not paste immediately upon selection but there’s a number of options like that to set it up to your liking.

source
- PhilipTheBucket@ponder.cat ⁨3⁩ ⁨days⁩ ago
  
  Just use KDE
  
  Gonna stop you right there 🙂
  
  and you get klipper which is an amazing clipboard manager
  
  Does it sync the select/middle-click clipboard with the Ctrl-C/Ctrl-V clipboard? I do like having both, especially since some tools will only be able to conveniently interact with one or another, it just drives me nuts that they are separate entities. Having a clipboard manager with history is a neat thing but not as essential to me as just having the nuts and bolts working.
  
  I can literally provide you a simple example: Go to emojipedia.org/slightly-smiling-face, click “copy”, and then come back and middle click in the reply. Do you get a smiling emoji? If you select some text in the reply and then hit Ctrl-V, do you then get the text you highlighted?
  
  source
baggins@lemmy.ca ⁨3⁩ ⁨days⁩ ago
Waow based

source
Im_old@lemmy.world ⁨3⁩ ⁨days⁩ ago
Hum, what’s the “second clipboard”? The one where you only highlight a text and then I can paste it with right click?

To me that’s amazing, I can (and do) use ctrl-c for some stuff and highlight for other.

As always, I like the flexibility.

Also I use vi 😜

source
- PhilipTheBucket@ponder.cat ⁨3⁩ ⁨days⁩ ago
  You should try Helix, it’s vi with some of the odd decisions removed and updated to adapt to some of the evolution (and stupidness, q.v.) that has happened in the Linux ecosystem but still true to a lot of the good stuff that vi does.
  
  I, too, like being able to both middle-click and to hit Ctrl-V. IDK how you got that I was unhappy about that part. What I don’t like is being unable to hit the “copy text” button in my web browser and then do anything at all to get that text into a terminal session, if for some crazy reason I might want to do that. But why, you ask, would I even need to do such a thing? I can always go back, carefully highlight this massive block of text character by character, like some kind of perfectly sensible person, and then carry the text over back to my terminal and middle-click it, like a person carrying an overflowing jug of water through a dance floor. You know what? Forget it, I can’t even remember what I was complaining about.
  
  MacOS, out of all the environments, actually has this worked out perfectly. Not only do they have only a single clipboard, but they have a very consistent set of keyboard shortcuts that supports both a modern and a Unixy workflow. You can use Ctrl-A (go to beginning of line), Ctrl-C (kill program), Ctrl-K, Ctrl-E, all the standard bash/emacs/terminal keyboard editing shortcuts, and they all do what you would expect if you’re a Unix person. But, you can also use Cmd-A (select all), Cmd-C (copy), and so on, and all those shortcuts do exactly what you would expect if you’re a Windows person. Every single program supports all of them consistently, and so it’s pretty easy to get done whatever you would want to get done whatever your accustomed workflow is.
  
  And then there’s Wayland over here like “NOT TODAY MOTHER FUCKER, THAT’S AN EDITOR RUNNING ON A DIFFERENT SERVER, JUST GIVE UP AND TYPE THE PASTE BACK IN BY HAND YOU FUCKING LOSER, YEAH THAT’S RIGHT, DID I STUTTER”
  
  source
  - CanadaPlus@lemmy.sdf.org ⁨2⁩ ⁨days⁩ ago
    Uhh, so I’ve been on Xfce for a while, and I’ve never seen this. When did the madness start?
    
    You mean into a GUI shell emulator, right? (I didn’t even know there was a clipboard that functions when not in a graphical session, otherwise)
    
    source
    -> View More Comments