5 ms·

That's your cut buffer. Heavy/Traditional Xorg users have enjoyed + gotten used to the multiple clipboards available. [1] Users are migrating to Linux from Wi

That's your cut buffer. Heavy/Traditional Xorg users have enjoyed + gotten used to the multiple clipboards available. [1] Users are migrating to Linux from Windows/MacOS and are not used to it; and asking for changes. (Remember Chrome + FF changing the selection behavior on the address bar to match windows?) [2] [3] [1] https://wiki.archlinux.org/index.php/Clipboard https://wiki.archlinux.org/index.php/Clipboard [2] https://bugs.chromium.org/p/chromium/issues/detail?id=26140 https://bugs.chromium.org/p/chromium/issues/detail?id=26140 [3] https://news.ycombinator.com/item?id=22832199 https://news.ycombinator.com/item?id=22832199

smabie 6y ago
I don't know what a cut buffer is is, but middle click copies to primary clipboard is the Windows style paste. I personally never really use clipboard, as using primarily is so much easier. I guess there might be using it at the same time, but I've personally never felt the need for two buffers at the same time.
- jasonjayr 6y ago
  I'm primarily an urxvt user: select copies & middle pastes. What terminal are you using that middle click is mapped to copy?
  - smabie 6y ago
    Sorry, i meant paste on middle click.
- owl57 6y ago
  > I've personally never felt the need for two buffers at the same time I find two buffers convenient when grabbing both url and title for a hyperlink.
- boring_twenties 6y ago
  I use both, but I admit it's a bit idiosyncratic. When immediately pasting after copying, the primary X buffer is obviously superior as it requires fewer actions, and only one hand. However, if I'm selecting something to keep in the buffer for a bit before pasting, I'd often screw myself by overwriting the buffer via random clicks in between. Now I'm in the habit of using primary in the cases when I know I already have an input field or prompt ready and waiting, and the very next thing I'm going to do is paste. When there are steps left to be performed after copy but before paste, I use the clipboard. I know it sounds overcomplicated and perhaps insane, but it's actually totally automatic at this point, and doesn't feel like it costs any mental cycles at all. For the first case, either I just readied the other program for input within the last few seconds, or at least it's visibly waiting for input on my screen. If not, then Ctrl+C it is.

smabie 6y ago

I don't know what a cut buffer is is, but middle click copies to primary clipboard is the Windows style paste. I personally never really use clipboard, as using primarily is so much easier. I guess there might be using it at the same time, but I've personally never felt the need for two buffers at the same time.

jasonjayr 6y ago
I'm primarily an urxvt user: select copies & middle pastes. What terminal are you using that middle click is mapped to copy?
- smabie 6y ago
  Sorry, i meant paste on middle click.
owl57 6y ago
> I've personally never felt the need for two buffers at the same time I find two buffers convenient when grabbing both url and title for a hyperlink.
boring_twenties 6y ago
I use both, but I admit it's a bit idiosyncratic. When immediately pasting after copying, the primary X buffer is obviously superior as it requires fewer actions, and only one hand. However, if I'm selecting something to keep in the buffer for a bit before pasting, I'd often screw myself by overwriting the buffer via random clicks in between. Now I'm in the habit of using primary in the cases when I know I already have an input field or prompt ready and waiting, and the very next thing I'm going to do is paste. When there are steps left to be performed after copy but before paste, I use the clipboard. I know it sounds overcomplicated and perhaps insane, but it's actually totally automatic at this point, and doesn't feel like it costs any mental cycles at all. For the first case, either I just readied the other program for input within the last few seconds, or at least it's visibly waiting for input on my screen. If not, then Ctrl+C it is.