Codecov Report

Merging #8292 (ccc32f4) into master (2fa9384) will decrease coverage by 1.85%.
The diff coverage is 95.93%.

❗ Current head ccc32f4 differs from pull request most recent head e19f2a0. Consider uploading reports for the commit e19f2a0 to get more accurate results

@@            Coverage Diff             @@
##           master    #8292      +/-   ##
==========================================
- Coverage   89.58%   87.73%   -1.86%     
==========================================
  Files         148      148              
  Lines      167049   163420    -3629     
==========================================
- Hits       149659   143376    -6283     
- Misses      17390    20044    +2654     

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2fa9384...e19f2a0. Read the comment docs.

As someone noticed, doing the same when deleting text, which is basically yanking the text first, "zd" cannot be used, it is an existing command. But perhaps that is OK, since when deleting the text you would still want the whole block to be deleted, only the yanking would omit the trailing spaces. So it could be a three step operation:

• select the block, use the new zy command to yank the text without trailing spaces
• gv to reselect the block
• "_d delete without yanking

Still, that requires typing three commands. I don't see an obvious two-letter command we could use for this.

oh, where did my test go?

looks like test failures are unrelated.

There are 2 different use cases:

Take a block like this:

aa
bbbbb
ccc

You can block select this <C-V>2j$ and you will have only the actual content (e.g. different line length in your register) when yanking. However, when pasting a block using p Vim will add padding (trailing white space) so that a rectangular block is pasted (so padding is added). zp will prevent adding the padding on paste, however it does not look at the actual register content, so if you have trailing whitespace in the register, it will get pasted as expected.

You have a whitespace-delimited block like this:

aaaa      text to yank                     ccccc
aa        some more text to yank           ccccccc
aaaaa     this text to yank is very long   cccccccc

Now, if you visual select column 2 using <c-v>2jtc you will yank the complete block, including the delimiting white-space. Possibly, in that case you are more interested in just the text and not in the whitespace at the end. If you care about the whitespace, use y to yank and it will be included in the register and later be put when using the p command family (even with zp). But you may have to clean up the trailing whitespace after pasting.

This can be prevented by using the zy command. It will only copy the actual content and leave the trailing whitespace out. So your register contains a block that in the end looks similar to what is in the register after example 1. However, when pasting using the p command Vim will add padding and make it a rectangular block (see example 1), except when using zp you will again only put the actual register content.

This case also happens for example 1, when you have :set virtualedit=block set.

but sometime you may not know what kind of 'yank' should be done at first.

I think the user knows what he actually wants so can decide depending on his actual requirements, so this is okay.

the cmd also is clear and simplest, no need another 'zy' cmd.

As shown, there are difference use cases, that each command covers, so a zy and zp are actually needed.