Also, is there any way to disable this behavior? I'm happier knowing
that only d, c, s, 'x, and y put things into the unnamed buffer.
No, it cannot be disabled. Deleted text always has to go somewhere.
I agree that this isn't easy to understand. Let me add this text to the
help:
Better idea: instead of just p, hit 0p to always paste from the yank
register. Or even use a mapping like :vnoremap p 0p
I see -- that makes sense. The downside of that particular remap is that
sometimes I might want to paste out of another buffer. But 0p is better
than having to do a p and
I've looked in:
:help v_p
:help registers
and I cannot find this behavior documented, and so I wonder if it's a bug.
If I visually select a block and hit p to paste from the unnamed
buffer, the block I'm overwriting gets put into the unnamed buffer.
There are two strange
On Feb 24, 9:45 am, Ted Pavlic t...@tedpavlic.com wrote:
I've looked in:
:help v_p
:help registers
and I cannot find this behavior documented, and so I wonder if it's a bug.
It looks like it is documented...sort of. From :help v_p:
(Implementation detail:
it actually
Hello,
Ben Fritz fritzophre...@gmail.com wrote :
Also, is there any way to disable this behavior? I'm happier
knowing that only d, c, s, 'x, and y put things into the
unnamed buffer.
:vnoremap p _d0P or similar ought to do it.
In order to avoid overwriting the @ register, but still
Ted Pavlic wrote:
I've looked in:
:help v_p
:help registers
and I cannot find this behavior documented, and so I wonder if it's a bug.
If I visually select a block and hit p to paste from the unnamed
buffer, the block I'm overwriting gets put into the unnamed buffer.
