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

Fix / Support cutting into the black hole register with "C" #2504

Closed
jiripospisil opened this issue Apr 2, 2018 · 3 comments · Fixed by #3927
Closed

Fix / Support cutting into the black hole register with "C" #2504

jiripospisil opened this issue Apr 2, 2018 · 3 comments · Fixed by #3927

Comments

@jiripospisil
Copy link

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

A bug report? I'm not not sure if it's worked before.

What happened:

Cutting into the black hole register doesn't seem to work with C. Position your cursor at the very beginning of a line with some text and press:

"_C

It should cut the whole line and store in the black hole register (throw it away). Instead, it does nothing. Interestingly "_c$ works correctly.

Environment:

  • Extension (VsCodeVim) version: v0.11.3
  • VSCode version: 1.21.1
  • OS version: macOS 10.13.4
@anonimitoraf
Copy link

anonimitoraf commented Nov 17, 2018

I found that this fixes it: https://github.com/anonimitoraf/Vim/commit/1899aeee186129203c6b453f4685a913f35bf1c2

@jpoon I see that this code was last edited a year ago. Do you remember why mustBeFirstKey is set to true?

@sobjornstad
Copy link

I'm experiencing this as well. It doesn't work with any register, not just the black hole register.

@J-Fields
Copy link
Member

The problem is here: https://github.com/VSCodeVim/Vim/blob/master/src/actions/commands/actions.ts#L2527
Not sure why C is enforced to be the first keystroke; 2C works fine in vim, for instance.

jpoon pushed a commit that referenced this issue Jul 29, 2019
I'm not 100% sure that there wasn't a reason why mustBeFirstKey was true, but I can't see what it would be.
Fixes #2504
stevenguh pushed a commit to stevenguh/Vim that referenced this issue Aug 27, 2019
I'm not 100% sure that there wasn't a reason why mustBeFirstKey was true, but I can't see what it would be.
Fixes VSCodeVim#2504
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.

5 participants