Normally vim doesn't touch the system clipboard unless you explicitly configure it to do so (e.g. clipboard=unnamed[plus]). I normally add separate Ctrl+C etc. bindings to operate on the system clipboard when I need to.
With Inkdrop the delete/yank commands appear to operate on the system clipboard. I constantly trip over this.
For example, I will:
- Copy something to the clipboard from another app
- Switch to Inkdrop
- Delete some text that I want to replace
- Attempt to paste the text I copied in (1) only for it to paste the text from (3)
Is there any way to get Inkdrop's yank/delete bindings to operate on an internal buffer (like vim's unnamed buffer) while having Ctrl+C etc. operate on the system clipboard?
Normally vim doesn't touch the system clipboard unless you explicitly configure it to do so (e.g.
clipboard=unnamed[plus]). I normally add separate Ctrl+C etc. bindings to operate on the system clipboard when I need to.With Inkdrop the delete/yank commands appear to operate on the system clipboard. I constantly trip over this.
For example, I will:
Is there any way to get Inkdrop's yank/delete bindings to operate on an internal buffer (like vim's unnamed buffer) while having Ctrl+C etc. operate on the system clipboard?