Shift+Ins vs. Middle Mouse Button

DAT , 10 months ago

nah

that’s some age old struggle

idk how people still justify that clusterfuck, but it’s that way since forever. I remember vividly how we were annoyed by such shit with some “cross platform” gui toolkits (or browsers) back when debian woody still was relevant.

This won’t be solved in this decade. or the next.

twistypencil , 10 months ago

Such stupidity, this drives me nuts

feral_hedgehog , 10 months ago

There’s a bug open for Firefox and you can change VSCode’s behavior by putting this in your keybindings.json:

<span style="color:#323232;">{
</span><span style="color:#323232;">    "key": "shift+insert",
</span><span style="color:#323232;">    "command": "editor.action.selectionClipboardPaste",
</span><span style="color:#323232;">    "when": "textInputFocus &amp;&amp; !editorReadonly"
</span><span style="color:#323232;">}
</span>

Not sure why either of them are messing with a “standard” shortcut…
If you want a more system-wide solution there are utilities that let you sync the PRIMARY (on selection) and CLIPBOARD (Ctrl+c) buffers mentioned in the Arch Wiki entry.

feral_hedgehog , 10 months ago

Looked around some more - maybe it’s because they’re all GTK apps?
unix.stackexchange.com/…/why-does-shiftinsert-pas…

ipsirc , 10 months ago

<span style="color:#323232;">autocutsel -cutbuffer 0 -f -s PRIMARY
</span><span style="color:#323232;">autocutsel -f -s CLIPBOARD
</span>

tal , 10 months ago

If you merge CLIPBOARD and PRIMARY, every time you select text, you'll wipe out the contents of CLIPBOARD. You won't be able to copy text, then do any work that involves selecting text, then paste.