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

The . (last inserted text) register should be read-only #3604

Closed
J-Fields opened this issue Mar 20, 2019 · 0 comments · Fixed by #3728
Closed

The . (last inserted text) register should be read-only #3604

J-Fields opened this issue Mar 20, 2019 · 0 comments · Fixed by #3728

Comments

@J-Fields
Copy link
Member

Describe the bug
You can currently copy arbitrary text into the . register. This is not how vim behaves.

To Reproduce
Steps to reproduce the behavior:

  1. Insert some text
  2. Use :reg to verify the inserted text is in the . register
  3. Copy some other text into the register with ".yw, for instance
  4. Use :reg to verify the copied text is in the . register

Expected behavior
Step 3. above should be a no-op, and in step 4., the originally inserted text should show in :reg

Environment (please complete the following information):

  • Extension (VsCodeVim) version: 1.2.0
  • VSCode version: 1.32.3
  • OS: Windows 10
jpoon pushed a commit that referenced this issue May 6, 2019
* Implement / (search) register

Fixes #3542

* Implement read-only registers

Fixes #3604

* Implement % (file name) register

Refs #3605

* Implement : (command) register

Fixes #3605

* Do not display _ (black hole) register in :reg output

Fixes #3606

* :reg can take multiple arguments

When it does, it lists only the registers given as an argument.
Fixes #3610

* Allow the : (command) register to be used as a macro to repeat the command

Fixes #1775
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants