I still don't get buffers
I still don't get buffers
An excellent option to have when one of the major use cases for clipboards is as an intermediary for password managers.
I hope they eventually get sued into the fucking ground.
Nah that’d be too intuitive
In all seriousness though, I kinda appreciate moving things around in my editor without losing that one snipet I copied for later
Application specific buffers are the first thing I disable on emacs. The OS one isn’t just integrated with every other normal piece of software, it’s also more powerful and easier to use.
… at least on my Linux, YMMV.
Yes. X11 replaced X10’s obsolete cut buffers (which can be modified by any process) with state-of-the-art selections. There are three selections in X11: a primary, a secondary, and a clipboard.
In modern desktops, the primary selection is overwritten every time you select some text (including in the terminal), which makes its content very ephemeral. You can paste it with the middle mouse button.
The secondary selection is generally not used, but it’s present in the specification, and you can use xclip -selection secondary to access it. Wayland doesn’t seem to have a secondary selection.
The clipboard selection is what most people understand to be THE clipboard. You have to write to it explicitly (through a keyboard shortcut, API, or CLI tool), and its content persists until it is overwritten, explicitly cleared, or the X server is killed. While the primary and secondary can only contain text, the clipboard can contain many kinds of data.
Not exactly. When you select a text and copy it, the two selections will end up containing the same text, but you can write to either selection without affecing the other by using an API, e.g. a website’s “copy to clipboard” button, or xclip/wl-copy.
Clipboard managers with a history feature are an altogether different layer on top of the standard selections. Plasma’s clipboard manager only cares about the clipboard selection, and even then, there are exceptions (e.g. copying a password for KeepassXC doesn’t save it in the history).
In modern desktops, the primary selection is overwritten every time you select some text
( °O°)
You just opened a whole new world for me, it works in Wayland too
then theyre all ignored by x-clip
xD
github.com/mg979/vim-visual-multi
I also missed multiple courses, but I started using vim-visual-multi in my nvim config and it’s been great. There’s a few others I tried that I couldn’t get to work quite right (usually some weird conflict with nvim-cmp) but I’ve had the best success with vim-visual-multi.
yah ive been swapping to hx wherever i need to do refactoring, it’s too good to miss out.
space-r ename symbol for easymode.
This feels like something I also do in neovim unless I’m misunderstanding you completely. Is it highlighting text and having yoir search apply just to the highlighted text?
If so, yes it’s great whenever you use it
ive never had to think about clipboard buffers until i used a modal editor.
now i spend %60 of my time trying to figure out where the copied symbol went.
yah, helix has that in the info bar oob.
im just not thinking about that when im copying shit, i just want to copy paste like it’s 1999.
You can see all registers in use with :registers, to paste from a register say "2 in insert mode use key combination <ctrl-r>2 or in normal mode "2p. You can check out more in :help registers. Unnamed register or “” is the system clipboard I think. To copy texts in a register you can prepend yank (/delete/cut, etc.) with that register "_ (for black hole register[^black_hole])
This is for neovim. Have keybinds for them and there saved you a plugin :D
[^black_hole]: Text yanked in this register is gone, i.e. it’s not saved in any register.
nano
esc… then : then q and ! or did I get the order wrong? Can’t I just ctrl+o ctrl+x?
Obligatory boo and/or hiss
I’ve also been meaning to give emacs a try but haven’t found the time or energy to figure out how to exit vim
I’m just an emacs … enjoyer (…?) and I just don’t understand the post. I’m pretty sure buffers here refer to something different from emacs buffers as they’re completely unrelated to clipboards. Then from a quick scan of the plug-in mentioned it seems to mimic the clipboard ring emacs has had for many decades (always?).
Basically I have no idea what’s going on here.