Has anyone separated their system clipboard from their emacs clipboard? I've followed the advice in https://stackoverflow.com/questions/24196020/how-to-stop-emacs-from-contaminating-the-clipboard but it has not appeared to make a difference. Deleting anything still overwrites my system clipboard.
@jayzawrotny no, haven't had the need to separate system clipboard and Emacs kill ring. I don't understand why you would need to do this, sorry.
In Spacemacs I use the paste transient state, so I can easily cycle through the kill ring history
https://github.com/practicalli/spacemacs-config/blob/master/.spacemacs.d/init.el#L385
I don't do a lot editing outside of Emacs, so don't need to worry about what Emacs puts on the kills ring for other apps. If I want to paste something from the system clipboard, I expect it to be the last thing I put on the Emacs kill ring.
On the fairly rare occasion I need to paste something into Emacs before deleting, well that is what I do. In Vim style editing it makes much more sense to do that, as they you can use d t
to delete to what ever character is after the end of the text you no longer want.
Sorry I can't be of more help.
I found the Emacs for MacOSX install to be the only one worth installing.
My brain thinks the way vim works where I can copy code after researching a workaround in docker, bash, w/e then go into the editor, delete or change text, then paste the text from clipboard. I’ll do my best to adapt but I still like using vscode + vim, atom + vim, and vim so clipboard consistency would be appreciated.
paste-transient-state
has never worked for me. I'm only now realizing that that's because it only works if you use p
in normal mode to paste, not if you use CMD p
from the osx
layer.
Playing with that myself. It’s going to take some time to get used to that if I can’t separate the clipboards. I also found if you do paste with cmd v and press M-y
it cycles as well, which feels a bit more accessible to me.