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.

Sign up for GitHub

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

Jump to bottom

:reg should not show the _ (black hole) register #3606

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

:reg should not show the _ (black hole) register #3606

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

Comments

@J-Fields
Copy link
Member

Describe the bug
:reg should not show the _ (black hole) register. This is not consistent with how vim behaves, and it's not useful because it can never contain anything.

To Reproduce
Steps to reproduce the behavior:

  1. Run :reg
  2. Observe that the _ register is listed

Expected behavior
It should not be listed.

  • Extension (VsCodeVim) version: 1.2.0
  • VSCode version: 1.32.3
  • OS: Windows 10
@J-Fields J-Fields mentioned this issue Mar 20, 2019
Closed
@J-Fields J-Fields mentioned this issue May 5, 2019
Merged
jpoon pushed a commit that referenced this issue May 6, 2019
@J-Fields @jpoon
Various improvements to registers (#3728)
1ef304e 
* 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
Assignees
No one assigned
Labels
kind/enhancement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Various improvements to registers
2 participants
@jpoon @J-Fields