Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Environment:
What happened:
Hello.
I think it's bug.
When I use VisualBlock mode(Ctrl+v),
I selected a word(just a word), press y and paste this where I want to insert using (p or P).
Then, you can see insert that word with newline.
What did you expect to happen:
When I insert that word, remove whitespace as newline.
How to reproduce it:
Always.
Ctrl+v , select a any word, copy that word using y, paste using a key(p or P)
You can see insert whitespace(new line).
I have the same bug, I copy and replace the whole line a lot and it always inserts a newline above.
how to reproduce:
Yank a line with yy
Select another line with V and replace with p.
same issue to me. and how can i fix it
yep, very annoying bug
Any news on this one?
+1 Pretty confusing behavior, I even trained my muscle memory to instantly delete the excess line
kill me
Hello.
This bug still exist... (vscode: 1.25.1, vscode/vim: today master branch d03a473f)
Today I had set up the develop mode for vscode/vim even though I don't know typescript. 馃槩
I tried to catch a reason why this bug happen.
When I review this repo codes, I thought It's weird.
Please check this line.
First, I put logging code on Every Yank function on the operator.ts file.
And, I enabled VisualBlock mode, I selected a word(example: func), not whole line and finally push key y.
I found out the code line was called. Is it right calling?
If it's right, why did you put this code?
toCopy += line + '\n';
Why do we need a newline character in the case?
@9to6 probably because you can visual block select multiple lines. This possibly could create array from the iterator and then joining instead of appending to every line. Do we need a new line at the end if that's done?
@jhsu Yup. I fixed it.
People who feel be annoyed by this bug should check this PR.
And you can build this plugin on local.
I have a same problem. When will this bug be fixed.
ctrl+v, copy multiple lines
move to destination
ctrl+v, and then p (paste)
Likely in the next release
I havea same problem . I have update my vscode to the latest version.
Likely in the next release
The bug is still !
Likely in the next release
The bug is still !
Hasn't been a release 馃檪 I've been busy recently but have a branch where this is just about working, so I still intend to get it out soon.
Likely in the next release
The bug is still !
Hasn't been a release I've been busy recently but have a branch where this is just about working, so I still intend to get it out soon.
Thank you!
Looking forward to the new version !
Most helpful comment
Any news on this one?