Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change behaviour of v_P (Visual Mode Shift-P) to not change unnamed register as introduced in vim 8.2.4242 #3094

Open
1 task
AndreasMrq opened this issue Mar 8, 2024 · 1 comment · May be fixed by #3095
Open
1 task

Comments

@AndreasMrq
Copy link

AndreasMrq commented Mar 8, 2024

Feature category

  • Check(Type 'x') any that Applicable item:
    • [x ] Vim
    • Vim plugin

If the function you request is realized by Vim or Vim plugin,
When you link the URL that is related,
We will make it easier to understand its function.

Is your feature request related to a problem? Please describe.
I often want to keep the content of the unnamed register when pasting over a selection in visual mode. This behaviour was introduced in vim 8.2.4242 by differentiating between p ( will change unnamed register) and P (will not change unnamed register).

Describe the solution you'd like
When in Visual Mode I would like to have P not change the unnamed register.

Describe alternatives you've considered
Alternatives include yanking into named registers and then pasting from there. This is arguably more cumbersome.

Additional context
The described behaviour is already implemented in vim 8.2.4242 ( https://vimhelp.org/change.txt.html#v_P ), NeoVim (https://neovim.io/doc/user/change.html#v_P) also in the VsCode Vim Plugin.

Note:
Please refer to the following. The goals of this project are written.
https://github.com/VsVim/VsVim/blob/master/Documentation/Project%20Goals.md

@nosami
Copy link
Collaborator

nosami commented Mar 8, 2024

This seems like it would be a good change. I didn't know about this feature and the old behaviour always used to catch me out.

nosami added a commit that referenced this issue Mar 9, 2024
@nosami nosami linked a pull request Mar 9, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants